Everything that describes your business counts.
Medjay builds the spec of your company, joint by joint, from what's written, what's said and what's observed, then confirms it with the people who do the work.
“If we had an hour to fix your business, we’d spend 55 minutes understanding it.”
Start with what you have. Observe only where it matters.
Every company sits somewhere between thorough, current documentation and almost nothing written down. The more you already have, the faster the inspection goes. Where the record is thin, observation and conversation fill the gaps.
You and your experts decide how far to go. Medjay shows you what's still unverified along the way.
Mostly undocumented
Observation and conversation do more of the work, and every gap they close gets written down for good.
Well documented
Observation mostly confirms what's already written down. The fastest path to a confirmed spec.
Every team sits somewhere different
[Illustration, not real data]
The teams that move fastest usually write down the least. The inspection meets each one where it is.
- FinanceControls, close checklists and audits keep a lot written down.
- HRPolicies and job descriptions exist, though they drift from daily practice.
- ITSystems are documented; the workarounds around them usually aren't.
- OperationsAdapting every day, so the real process lives in people's habits.
- SalesMoving fast; much of how deals get done lives in a few people's heads.
Three kinds of evidence
We're building the spec of every bolt, beam and weld in your business, so everything that describes it is useful.
What's written
- Policies and SOPs
- Process documentation
- Job descriptions
- OKRs and strategy decks
- Process captures from tools like Scribe
What's said
- Meeting recordings and transcripts
- Interviews, including advisor interviews
- Surveys
- Conversations in Clarion
What's observed
- Voyager, on the desktop
- Only where and when you decide
- The systems, handoffs and workarounds nobody wrote down
Everything else is raw material. The confirmed spec is the product.
Declared. Observed. Confirmed.
Declared
What the business says about itself: the documents, the org chart, what people tell you.
Observed
What actually happens, seen in the work itself.
Confirmed
What the person who owns that joint has reviewed and agreed is true, with their name attached.
[Illustration, not real data]
- Confirmed
- Declared or observed, not yet confirmed
- Still unknown
What's still unverified is your progress bar.
Four keys, one Ground Truth.
Each key adds to the same living spec of your company.
Voyager
1. Gather context
Bring in what already describes the business, from policies and process docs to meeting transcripts, and use Voyager to capture real work where it makes sense.
Clarion
2. Process context
Clarion organizes it all into findings and scores, like your Clarity Score, so you can see where you're clear and where you're not.
Ask Ricky
3. Verify context
The people who own each part confirm what's true, with your advisor and with Ask Ricky, so nobody writes down a guess.
More about Ask Ricky →
Sentinel
4. Use the Ground Truth
What's verified becomes the foundation for reports, SOPs and training, and Sentinel tells you when reality starts drifting from it.
What we ask of your team
Good consulting has always started with observation. The question is which kind fits each part of your business.
Consultants have always watched how work gets done: in person, with flow charts, SIPOC and value stream maps, recorded meetings, and workflows drawn together on a shared whiteboard. We use all of these where they fit. Every kind of observation shapes what it sees; people work a little differently with someone looking over their shoulder. So we choose the lightest touch that still shows the real day.
Observing the work as it happens.
Voyager records only on the computers it’s installed on. It captures the work as it’s really done, without anyone standing over a shoulder. It asks the least of your people and shows what nobody thinks to mention.
Walking us through it.
Where Voyager isn’t used, people show us their work in a Teams or Google Meet recording, in interviews, and by mapping it with us. It takes more of their time, and it tends to show a smoother day than the real one.
- Your people stay in the picture. We walk through what we observed with the people who do the work, and they help shape how it changes from here.
- Privacy built in. You choose which apps and sites are never captured, and Moments can be redacted.
People who work away from a desk, in the field or on the road, take part through short conversations and check-ins.
What everyone does either way
Answer short questions.
Quick surveys and questions in a chat with Ricky, our AI assistant, by typing or by voice.
Share what they’ve written.
SOPs, and the notes they’ve made so others can cover for them when they’re out.
Capture moments.
A quick screenshot when something works great, like a tool they’d hate to lose, or when something frustrates them and could be better.
Join the conversations.
The most important part. Some are one-on-one with your advisor; some are small or medium groups across teams, with leaders and the people doing the work, talking through how and why things are done today and what could be better.
What you end up with
A confirmed spec of how your company actually runs, including the parts no system ever recorded.
Tech stack reality.
Which systems are actually used, and which ones aren't.
Process truth.
How work actually flows, not only how the SOP says it should.
Knowledge patterns.
Where expertise lives, and what happens when it walks out the door.
Decision points.
Not just what was decided, but the context and constraints behind it.
Load-bearing workarounds.
The side systems and habits people built to keep things moving.
Know what your company can carry today, and what has to change to carry the next plan.