Cycle length accepted as given
Regulation absorbs blame that process design should carry.
Who we helpFinancial Services
The dysfunction hides inside process, not inside speed.
Long cycles, heavy compliance and several internal stakeholders on every deal. Nothing about that looks broken from outside, which is exactly why the cost sits undiscovered longer here.
Sector read
Process hides what speed would expose.
Handoffs nobody owns
Relationship, product and risk meet without an end-to-end owner.
Process hiding dysfunction
Controls make the system look orderly rather than legible.
Risk enters the deal late
Compliance meets the opportunity after its shape is already fixed.
Cross-sell assumed, not designed
Relationship breadth is expected without a route built to it.
Where the time collects
Necessary control and avoidable drag look identical from outside.
Both produce a long cycle. Separating them is the first job, and nothing downstream can be priced until it is done.
The symptom is reported at the surface. The cause sits underneath it.
Long cycles read as compliance
Duration is attributed to regulation before anyone separates the queue from the wait.
Surface · what gets reportedRelationship, product and risk each own a piece
None of them owns the deal moving between the pieces.
Structure · what produces itProcess makes the system look orderly
Controls make it legible to an auditor and illegible to the people running it.
System · where it breaksTime and deals go missing at sign-off
The gap between necessary control and avoidable drag is never separated, so neither is managed.
Consequence · what it costsCause and consequence rarely surface in the same place.
What it looks for here
Separate necessary control from avoidable commercial drag.
The dysfunction families do not change for financial services, and regulation is not treated as an automatic explanation for every delay. The diagnostic separates what the regulatory environment genuinely requires from avoidable coordination burden, then follows the evidence across relationship, product, risk and operations.
- Relationship, product and risk
- Compliance and operations
- Deal desk and pricing exceptions
- Deal-cycle logs
- Incentive design
- Exception paths and sign-off timestamps
Long cycles and heavy process change how the strain presents.
What tends to break first
Ownership splits before anyone notices it has.
Process discipline makes the system look orderly for longer than it is. The strain accumulates at the boundaries between the functions that each own part of a deal.
Split ownership
Relationship, product and risk each hold a piece. No single owner is accountable for the whole path, so the gaps between them belong to nobody.
Sign-off transitions
Time and deals go missing at the point of handover to approval. Each step is defensible and the sequence is not.
Cycle attribution
Long cycles are read as compliance cost. Some of that is real; the part produced by coordination is folded into the same explanation.
Evidence flow
Process artefacts record that steps happened, not whether the criteria were met, so the record looks complete while the decision quality is unexamined.
What happens next
Three ways in, depending on what the evidence already says.
Executive Workshop
Three hours with the people who can change the system. One condition named, in writing, before any evidence is gathered.
Explore the Workshop →Diagnosis
Interviews, the records you already produce and your own rates. What is breaking, what it costs, what to change first.
Explore the Diagnosis →Strain Check
Ten questions, two minutes. A first read on which part of your commercial system is carrying the most strain.
Take the Strain Check → FAQ
Before you assume the cycle is just how it is.
How do you separate genuine compliance requirements from process that just grew that way?
Through the interviews and a review of the process documentation itself. Compliance requirements are usually written down somewhere specific, and steps that exist for other reasons rarely have the same clear origin when traced back.
Our sales cycle is long by design, does the diagnostic account for that?
Yes. The method reads your baseline against your own system, not against a shorter-cycle sector, so a genuinely long cycle is not mistaken for a broken one.
Multiple departments touch every deal here, who gets interviewed?
Relationship, product and risk are typically all included, since the handoffs between them are where this sector's dysfunction tends to concentrate. The exact list is agreed with you before the engagement starts.
Is client and deal data handled under the same confidentiality standard as elsewhere?
Yes, data gathered inside an engagement is governed by that engagement's own confidentiality terms, handled securely and never reused outside it without written permission.
Get started
Compliance explains some of the drag. A number shows how much of the rest is choice.
Use 30 minutes to define the operating question, test what evidence exists and decide whether Kihon has a role at all. No scope is proposed before that is clear.
Discuss the operating problem