01 / Leadership change
Your next CTO needs context.
A search, planned departure, or interim-to-permanent handover creates a reason to investigate what the new leader will inherit.
Explore CTO transitionIndependent research for business decisions
Your company's knowledge is scattered across people, decisions, data and software. We connect the evidence, test what's driving the result and help leadership decide what to change.
When to bring us in
01 / Leadership change
A search, planned departure, or interim-to-permanent handover creates a reason to investigate what the new leader will inherit.
Explore CTO transition02 / Unexplained friction
Work stalls between teams. Numbers do not reconcile. We trace the question across people, records, and systems rather than accepting the first explanation.
03 / A proposed change
Before replacing a system or investing in AI, check the data, permissions, dependencies, and operating reality. The evidence may support a change, a smaller step, or no change yet.
How it works
Senior researchers choose the questions and test competing explanations. AI expands the evidence we can explore; technology, people and analytics specialists determine what it means for the decision.
Senior researchers use MemoryOS and AI-assisted tools to follow decisions, connect sources and explore competing explanations.
Questions and findings are tested and refined throughout.
Our technology, HR and analytics specialists challenge explanations together and identify what matters for the decision.
The evidence supports practical priorities and makes open questions visible.
Systems, workflows, decisions and responsibilities connected.
Tested explanations, source references and open questions.
30/60/90 priorities, owner roles and validation checks.
Review the reasoning and next decisions with leadership.
Question / Explore / Connect / Hypothesize / Test / Refine
Explore the diagnostic methodWhat you receive
Four connected results for leadership to examine, challenge and put to work.
01 / Operating Map
Systems, workflows, decisions, responsibilities and dependencies around the question leadership needs answered.
02 / Evidence-Backed Findings
Findings linked to source evidence, with competing explanations, confidence and the questions that still need an answer.
03 / Intervention Plan
30/60/90-day priorities, proposed owners, dependencies and checks for progress, with a brief for the first recommended change.
04 / Management Handover
A working session with leadership to examine the evidence, challenge the conclusions and agree how to use the findings.
The research record connects all four results, so leadership can return to the evidence as decisions develop.
See diagnostic scope and deliverablesTrust comes first
We do not publish client records or findings as case studies. Our public examples are fictional. The work we do with your company is for the people you authorize to receive it.
See how an investigation worksSenior judgment
Technology, people and analytics specialists shape the inquiry and challenge the explanation together.
Michal leads the investigation and brings the right expertise to your question.
Meet the experts and their rolesA focused engagement
We agree one material operating question and follow the evidence across the teams and systems that shape it. The standard engagement runs for four weeks after agreed access is available.
Read the service scope and deliverablesYou know the question, team, deliverables, schedule and fixed fee before work starts.
The handover gives leadership a supported view of what to change and in what order. Any subsequent implementation is agreed separately.
Frequently asked questions
No. Start with a concrete concern or decision: conflicting reports, a stalled workflow, a leadership transition, or a proposed investment. We agree an investigation question and achievable scope before starting. The four-week schedule depends on the agreed access being available.
Access is agreed for the selected scope. It may include conversations, transcripts, documents, code, configurations, and read-only system data. Necessary sources, exclusions, and access restrictions are documented before work begins.
A typical engagement includes 10–20 stakeholder interviews and 10–20 detailed written discovery questions, adjusted to the problem and team structure. A sponsor must also be available to resolve access and ownership decisions.
Work is performed remotely in a Google Cloud environment provisioned and controlled by your company. Blatt does not require company records to be uploaded to a Blatt-owned production environment.
Senior researchers direct the inquiry and use AI to explore approved records, trace connections and test more explanations. Model requests use your company's API access and may go to the selected external provider under the agreed handling terms.
The engagement delivers research, a prioritized plan and a management handover. Implementation, including a focused first change, is agreed separately.
The finding will say what was checked, what the records support, and what remains unknown. That can change the recommendation—including a decision not to proceed with a proposed system change or AI investment.
Ongoing access can be arranged separately. The proposal distinguishes the portable project deliverables from access to Blatt's proprietary research infrastructure, hosting, updates, and support.
Start with your situation
Tell us the decision, what seems unclear, and your timing. We will discuss whether a bounded diagnostic is the right next step.