Advisory
Three sessions. One decision. The answer in writing.
I start with what your business needs to achieve, then work through the technology with you. I bring the framework and judgment. Your team brings the measurements.
Decisions we can work through
- Should we replace this platform, or fix the process around it?
- Where could AI reduce manual work, and what still needs human review?
- Which architecture supports our growth without adding unnecessary cost?
My consulting practice, Sereno Tech Consulting, now lives here.
The engagement
The Actual State Diagnostic
Three working sessions
Spread across about a month, with work for your team between each one.
For a decision with lasting consequences, where your team needs an outside perspective and evidence it can act on.
What you get
-
A decision brief
The decision, what closing it looks like, and what would make me wrong. Written in session one, before any data exists.
-
The option list
Every route to the outcome, including the ones you already threw out.
-
A measurement plan
What your team captures between sessions, and which argument each number settles.
-
Diagrams of what is really happening
Your traffic, your money, your people. Not the architecture on the wiki.
-
The recommendation, in writing
One route, the evidence that closed it, and what would change the answer.
-
The loop, so you can run the next one
Templates and working files with your business already in them. The next one, you run.
How it runs
Three sessions, and the work between them.
We work through it together. Between sessions your team gathers what only your team can get, and the next session runs on what comes back, so if it is not ready we move the date rather than guess.
-
Session one
The decision, and every route to it
Write down the decision, what closing it looks like, and what would make me wrong. Then open every route, including the ones you already threw out.
-
Your team
Go and measure
You leave with a measurement plan. Your people get this faster than any outsider, and you keep it.
-
Session two
What the numbers actually say
We read what came back against what the plan claims, and I draw it. Routes the evidence rules out get struck.
-
Your team
Cost and test what is left
The survivors get priced against your real constraints, not the version in the deck.
-
Session three
The decision, written
One route, the evidence that closed it, and what would change the answer.
Underneath it are the same four moves I use on a fault, an architecture, a company or a market. The full framework.
Not that yet
Or learn to run it yourself
The same four moves, with the templates I use in the sessions. For a small team that wants this done in-house.
Not built yet. Tell me what you are working on and I will let you know when it opens.
Tell me what you are working on