Skip to content
For business clients only. By opening Stripe Checkout, you confirm that you are acting for a business or professional organization.
01Signal Library
Signal Library
Execution signals, translated into decisions leaders can use.
Short reads that help leaders name the real execution break before they buy the next
tool, workshop, program, or consulting scope.
02Nine pillar briefings
Read for the decision underneath the topic.
Nine pillar briefings. Each one is laid out the same way: the symptom you can see, the system break underneath it, and the next move.
01Recognize the symptom
Start with the visible pain, but do not stop there. Look for the symptom that keeps showing up across meetings, tools, processes and governance layers.
02Name the system break
Separate noise from structure. The symptom is where it hurts; the break is where the system stopped carrying the work.
03Choose the next move
One move, narrow enough to run in thirty days and specific enough to prove the system can move at all.
01DEFINITION
The operating design that turns strategy into repeatable movement: ownership, decision rights, handoffs, governance, rhythm and value logic.
Read the briefing- Symptom
- Activity is rising and Monday still looks exactly the same.
- System break
- Nobody designed the system: ownership is partial, authority is unclear, governance protects comfort.
- Next move
- Answer the seven questions in plain language before the next spend is approved.
02FAILURE PATTERN
Transformations fail when the operating system underneath the ambition was never designed, ownership partial, decisions political, value late.
Read the briefing- Symptom
- The programme is busy and the same blockers return every single week.
- System break
- Five breaks: ownership, decision rights, handoffs, governance and value logic.
- Next move
- Follow one real path until it breaks. Redesign that path before scaling anything.
03S2P
A taxonomy is not documentation. It is a shared execution language for ownership, decisions, handoffs, controls, technology and value.
Read the briefing- Symptom
- Every region and function means something different by the same S2P word.
- System break
- The taxonomy names steps but not owners, decisions, handoffs or value signals.
- Next move
- Taxonomy-map one high-friction path: owner, decision, handoff, system, exception, value.
04AI READINESS
AI readiness is the moment the operating system can safely turn a signal into an owned decision and a governed action.
Read the briefing- Symptom
- There is an automation idea long before there is an owned decision.
- System break
- One of seven is missing: signal, ownership, decision rights, action path, data, governance, value.
- Next move
- Write one candidate path in plain language. If you cannot, it is not yet an AI problem.
05P2P
Six control points, and the cost of a correction rises at every one of them.
Read the briefing- Symptom
- Corrections keep landing late and each one costs more than the last.
- System break
- The control point that could have caught it sits downstream of where it broke.
- Next move
- Move one control upstream to the earliest point that can still catch the correction.
06S2P
The seven seams where Source-to-Pay breaks, and why leakage starts at the first handover.
Read the briefing- Symptom
- Value leaks and nobody can say where the leak actually started.
- System break
- Seven seams. The first handover is where the leakage begins and where nobody is looking.
- Next move
- Instrument the first handover before touching the platform.
07OPERATING MODEL
Ownership, decision rights and governance made executable across business units.
Read the briefing- Symptom
- Four business units execute the same mandate four different ways.
- System break
- Ownership and decision rights were drawn on a chart, never made executable.
- Next move
- Decide what must be common, what stays local, and who resolves the tension.
08GOVERNANCE
Governance works when it gives enough common architecture to move and enough local truth to stay executable.
Read the briefing- Symptom
- Every cross-unit decision needs a senior rescue to move at all.
- System break
- Governance is performative alignment: everyone represented, nobody able to decide.
- Next move
- For one recurring issue set owner, threshold, evidence, exception, cadence, then delete one meeting.
09DIAGNOSIS
The senior first move when the issue is too important for a generic workshop and too unclear for a large mandate.
Read the briefing- Symptom
- Leadership knows something is off but not which route to take.
- System break
- The break has not been named, so every proposed route is a guess with a price tag.
- Next move
- Name one owner, one decision, one handoff, one rhythm, one value signal.
KULIC SignalIf the same blocker returns quarterly, it is not a blocker. It is design.
03Insights · Signal Library
Six signals, each read down to the next move.
Six signals. Each one names what you see, what is actually broken and the next move, with the route that fits.
Four symptoms to look for
- Repeated escalationit keeps going up a level
- Manual workaroundthe fix is now the process
- Unclear ownershipeveryone, therefore no one
- Decision delaythe calendar decides
S-01Procurement transformation
Why transformations create activity instead of execution.
- WHAT YOU SEE
- Initiatives, dashboards and workshops multiply. The number does not move.
- WHAT IS ACTUALLY BROKEN
- Ownership and decision paths were never resolved, so activity substitutes for authority.
- THE NEXT MOVE
- Name the owner and the decision path before the next initiative is funded.
S-02S2P operating model
The real break lives between ownership, handoffs and decisions.
- WHAT YOU SEE
- Regions, process owners, IT, finance and procurement each define success differently.
- WHAT IS ACTUALLY BROKEN
- No one owns the seam between them, so every gap is closed with a local workaround.
- THE NEXT MOVE
- Map the handover chain and put a name on each seam before the next rollout wave.
S-03AI readiness
AI readiness starts before automation.
- WHAT YOU SEE
- Automation is on the roadmap while the process still runs on exceptions.
- WHAT IS ACTUALLY BROKEN
- Automating a fragmented operating model scales the confusion, not the throughput.
- THE NEXT MOVE
- Test whether the system can execute at all before you teach it to execute faster.
S-04Governance
Governance fails when decision rights are political.
- WHAT YOU SEE
- Nobody is sure who can decide, so everything travels up a level to be safe.
- WHAT IS ACTUALLY BROKEN
- Escalation has become the operating model and leadership time is the currency.
- THE NEXT MOVE
- Write down who decides what, at which threshold, and publish it. That is the intervention.
S-05Leadership alignment
Transformation needs language that survives Monday.
- WHAT YOU SEE
- The narrative lands in the room and evaporates before the next meeting.
- WHAT IS ACTUALLY BROKEN
- No cadence carries a decision from one week to the next; the story outruns the system.
- THE NEXT MOVE
- Give the decision a standing slot and an owner, or stop telling the story.
S-06Executive diagnosis
Diagnose before the expensive route.
- WHAT YOU SEE
- A small execution issue is being scoped as a large consulting programme.
- WHAT IS ACTUALLY BROKEN
- The problem was never named, so the response is sized by fear rather than by evidence.
- THE NEXT MOVE
- Buy the diagnosis, not the programme. The scope should follow the finding.
04Field index
Fifteen field signals, sorted by where the break sits.
Fifteen signals from practice in four lenses: ownership, process, governance and decision speed. Each entry gives the symptom, the fracture, the move and the moment it counts as closed.
Ownership5 signals
01Adoption doesn't happenThe system is live. Three months later half the organisation is still working in Excel.
- Fracture
- Nobody owns usage. The project owned the rollout, operations own operations; in between there is no one.
- Move
- Name one person per process whose objective is tied to adoption, not to go-live.
- Closed when
- When someone talks about their adoption rate in the next objective review without you asking.
02Technology introduced, behaviour unchangedThe tool is rolled out, trained and paid for. The work happens the way it always did.
- Fracture
- The old behaviour is still rewarded. As long as the workaround is the faster route, it is the rational choice.
- Move
- Find the fastest way around the system and make it more expensive than the way through it: organisationally, not morally.
- Closed when
- When someone takes the route through the system because it is faster, not because it is mandated.
03Pilots with no recipientFour AI pilots are running. None has reached regular operations.
- Fracture
- The pilot has a sponsor but no recipient. Nobody is obliged to take the result over.
- Move
- Approve the next pilot only once it is named who takes it into operations if it works: with a name and a budget.
- Closed when
- When a pilot is turned down because no recipient can be found, and that counts as a clean decision.
04The data is to blameEvery analysis ends at data quality. For two years now.
- Fracture
- Data has users but no owner. As long as quality belongs to everyone, nobody improves it.
- Move
- Assign one accountable person to each of the five most important data objects. Not a team. A person.
- Closed when
- When an analysis fails on data quality and a name comes up in the room instead of a department.
05The system hangs on one personWhen one particular person is on holiday, the process stops.
- Fracture
- A gap in the design is being bridged by a human being. As long as they bridge it, the gap stays invisible.
- Move
- Have that person note for one week which decisions they take that they are formally not responsible for. That is your design backlog.
- Closed when
- When that person takes leave and you only notice it in the calendar.
Process3 signals
06The handover under pressureAs long as nothing is burning, the handover between functions works. Under deadline pressure it stops.
- Fracture
- The handover point belongs to neither side. Each considers it the other's job, until it gets tight.
- Move
- For the three most critical handovers, name an owner of the transition itself, not of the two ends.
- Closed when
- When under the next deadline someone defends the handover instead of skipping it.
07Cycle time without a causeCycle time is going up. Everyone involved is working faster than last year.
- Fracture
- The time is not spent in the steps but between them: in waiting states that appear in no process description.
- Move
- On one real case, measure idle time instead of handling time. The difference is the process nobody designed.
- Closed when
- When in the next process discussion someone names a waiting time rather than a handling time.
08The detour is the faster routeA noticeable share of volume runs past the defined process.
- Fracture
- The standard route is longer than the exception route. That is not a discipline problem, it is a design fault.
- Move
- Measure the three most common bypasses and the standard route in days. Shorten the standard route before you ban the bypass.
- Closed when
- When volume on the standard route goes up without any rule having been tightened.
Governance4 signals
09Savings that never landThe savings report is green. Nobody can find the number in the P&L.
- Fracture
- There is no defined handover between the negotiated result and the budget line. The value gets reported, never booked.
- Move
- For every committed saving, define up front which budget it lands in and who signs it off there.
- Closed when
- When finance reports the saving before procurement does.
10Escalation as the operating modeThe calendar fills with escalation meetings. Every escalation gets a room; none gets a decision.
- Fracture
- Escalation has stopped being the exception path and become the only working decision path. The real operating model exists on paper only.
- Move
- Count for one week how many decisions regular governance actually made. If that is fewer than the escalations, governance is the problem.
- Closed when
- When an escalation meeting gets cancelled because the regular body has already decided the question.
11Everyone defines success differentlyEveryone supports the programme. In the status report the success criteria contradict each other.
- Fracture
- There is no shared target picture, only summed functional goals. The programme optimises six things at once and finishes none.
- Move
- Have each function write in one sentence how it measures success. Put the sentences side by side before building anything else.
- Closed when
- When two functions notice in the same meeting that their goals contradict each other and treat that as the outcome, not as an interruption.
12Green status, no progressThe programme has been green for six weeks. The delivery date has moved twice.
- Fracture
- Status measures activity, not state. What gets reported is effort, not capability gained.
- Move
- Replace one activity line in the status report with a state line: what can the organisation do today that it could not four weeks ago?
- Closed when
- When the status moves from green to amber without a date having moved.
Decision speed3 signals
13Too many initiativesEighteen initiatives in the portfolio. None finished, none stopped.
- Fracture
- Prioritisation is treated as analysis instead of an act of leadership. As long as nothing is cut, everything competes with everything.
- Move
- In the next portfolio review, cut two initiatives outright. Not paused. Cut.
- Closed when
- When the portfolio list is shorter after the review than before, and nobody asks where the two went.
14Decisions outside the systemThe decision has been made. It is nowhere in the system.
- Fracture
- Decision rights are described but not embedded in the flow. What gets decided in a corridor is faster. And invisible.
- Move
- Take the last ten material decisions and check how many are traceable in the system. The gap is your exposure.
- Closed when
- When someone disputes a decision and the argument ends at the record, not at somebody's memory.
15Alignment instead of decisionThe meeting is called alignment. It has been repeating weekly for a quarter.
- Fracture
- There is no body allowed to decide. Alignment substitutes for the decision because the decision belongs to nobody.
- Move
- On the next agenda, put a name and the word “decides” behind every item. Items without a name come off the agenda.
- Closed when
- When someone takes an item off the agenda because there is no name behind it.
THE FULL RECORD
12 ENTRIESTwelve working papers. All of them, in one place.
Ordered by depth, not by date. The long reads carry one argument from break to decision; the short orientations settle a single question. Every length is measured, not estimated.
THE LONG READS06
- 01Leadership Alignment: Language That Survives MondayLeadership alignment only matters when the language survives Monday: owners, decisions, handoffs, and the next move must become visible.1.335 WORDS
- 02Procurement Transformation: Activity Is Not ExecutionProcurement transformation fails when the system produces more activity than governed movement.1.261 WORDS
- 03Governance: Decision Rights Before EscalationWhen decision rights are unclear, escalation becomes the operating model and leadership time becomes the currency.1.216 WORDS
- 04Executive Diagnosis Before the Expensive RouteA senior diagnosis can prevent a small execution break from becoming a large, slow consulting machine.1.192 WORDS
- 05AI Readiness Before AutomationAI scales the operating model you already have.1.176 WORDS
- 06S2P Operating Model: Ownership Before RolloutS2P rollouts stall when ownership, handoffs, and decision rights are unclear before technology has to carry the operating model.949 WORDS
THE SHORT ORIENTATIONS06
- 07What Is Execution Architecture?Execution Architecture is the design of ownership, decision rights, handoffs, governance, operating rhythm, and value logic so transformation becomes executable.531 WORDS
- 08Why Procurement Transformations FailProcurement transformations fail when ownership, decision rights, governance, value logic, and operating-model reality are not designed as one execution system.527 WORDS
- 09S2P Process TaxonomyA practical executive briefing on S2P process taxonomy: how source-to-pay language, ownership, handoffs, decisions, and value logic become executable.454 WORDS
- 10AI Readiness for Procurement and S2PAI readiness for Procurement and S2P starts with the execution system: signal, owner, decision, data, governance, action path, and value logic before automation.413 WORDS
- 11Operating Model Governance for Organizations with Multiple Business UnitsOperating-model governance for multi-entity organizations: ownership, decision rights, escalation, handoffs and rhythm, without freezing local reality.399 WORDS
- 12Executive Diagnosis for Transformation LeadersExecutive Diagnosis helps transformation leaders find the likely execution break, decision bottleneck and practical 30-day move.386 WORDS