FULCRO01
Map of the Current Operation
How the work actually happens today, against what the organisation thinks it does.
Map
The practice
You won't end up dependent on me. You'll end up less dependent on everyone.
Me included. What remains is structure your team runs on its own, not a contract you renew so you don't lose what you learned.
Automated infrastructure
Why you can relax
Four things that take the risk off your desk.
- If your problem isn't an architecture problem, I say so in the first conversation. You leave with a reading and without an invoice.
- The person you talk to is the person who delivers. The person from the first conversation signs off the final architecture. There's no layer that promises and another that finds out later.
- The scope is defined before the price. Depth and measurement points come from what your operation demands, not from a fixed package.
- What I don't know is written down. You also get the list of what the evidence doesn't support, why, and what would need to be true to decide.
Architectural X-Ray
What you receive, item by item.
It's not a report. It's seven documents your team uses after I leave.
02
Technology Inventory
What's contracted, what's installed, and what's actually used.
Inventory
03
Maturity Diagnosis
The eight dimensions measured: processes, governance, information, technology, automation, indicators, security and artificial intelligence.
Diagnosis
04
Map of Bottlenecks
Each bottleneck with its impact, priority and a named owner. No "the team needs to align".
Bottlenecks
05
Target Architecture
The design of how the operation should work. Structure, not a choice of tool.
Architecture
06
Prioritised Roadmap
Order, effort, impact, and the bottleneck each action closes. With acceptance criteria to know whether it worked.
Roadmap
07
Executive Presentation
It ends in a decision ladder: the choices only you can make, and what changes with each way out.
Decision
If the X-Ray doesn't show you what you couldn't see before, you don't pay. It's not just my word: each of the seven deliverables has acceptance criteria, and you can check item by item whether it delivered.
The X-Ray goes as far as the decision made and the next step sized. It doesn't carry out the next step, and that's what makes the second cheque smaller than the first.
And it's one way to begin, not the only one. When the problem is already clear, the conversation starts straight away.
Who leads the work
Karinne Dias.
I spent ten years going into operations where no one had authority over all the parts, the deadline wouldn't move, and each country played by a different rule. Always the same work: making the person who decides see what only existed at the front line.
Where she has operated
Brazil, England, France and Jordan. International events, a sales-channel operation abroad, the education arm of a healthcare organisation, and a digital product from zero to a working shop.
What repeated
Coordinating parts that didn't answer to her, under a deadline that wouldn't move, across contexts that didn't share the same rules. The method came from there, not from a framework.
What she doesn't claim
Scale, a team or a queue of clients that don't exist. The practice is being built, and this site says so instead of suggesting size.
Why that's good for you
One person leads from first contact to delivery. Nothing is lost in the handoff between who sold and who executes, because there is no handoff.
Work delivered
Described by the scope delivered, not by an invented number.
Work only appears here with permission and with enough evidence to tell it precisely.
01
Vit
A custom link system, built from scratch for the client's operation. Contracted, delivered and in use.
Link
02
Airos
The densest scope so far. A product that didn't exist was created, photographed in a professional shoot and taken all the way to a working shop, end to end.
E-commerce
Start a conversation
Write the problem, stated, in three lines.
I'll reply telling you whether this is an architecture problem, and what I can already see from what you wrote. If it isn't, I say that too.
- You write what's stuck
You don't need the answer. You need the problem stated.
- I read it and send back a reading
No corporate deck and no sixty-page proposal.
- If it makes sense, we define scope
Before price, always in that order.
One person leads the whole of the work. That limits how many engagements run at once, and it's why the first conversation is about scope and not about selling.