When Speed Needed a Sequence

What an origin case is. This is not a Journey chapter, and it is not a claim that Adaptive Thinking existed as a method in 2020. It documents a piece of practice completed years before the method was named. Patterns later formalised through Adaptive Thinking are visible in this work in hindsight — they did not guide it at the time.

THE CASE

1. 01 · Three Loss-Making Markets
2. 02 · Two Views of Value
3. 03 · Three Markets in Two Weeks
4. 04 · Stabilisation Before Optimisation
5. 05 · From System Use to Organisational Ownership
6. 06 · Stopping the Leakage
7. 07 · The Three Clocks of Integration
8. 08 · What This Case Later Revealed

01

Three Loss-Making Markets

The acquisition covered three loss-making operations, in the Czech Republic, Slovakia and Hungary, together holding a combined portfolio of approximately EUR 30 million — broadly EUR 10 million per market. Each ran on a weak organisational structure, without an adequate integrated operating system; important processes and management information relied heavily on Excel.

The portfolio carried real leakage: expensive funding, an operating model that didn't fit the scale of the business, and non-earning stock — vehicles sitting without active customer contracts or clear ownership.

Due diligence reached a specific conclusion: the assets still had value. The existing operating system was what prevented the organisation from realising it.

The assets had value. The operating system prevented the organisation from realising it.

The work that followed was led in practice by Tomasz, then Deputy Regional CFO (Regional CFO from 2022) — not as a formally appointed PMI Director, but as the person holding the system together across due diligence, the business plan, migration, finance, pricing, risk and organisational structure.

02

Two Views of Value

Two distinct business plans framed the decision. The standalone view reflected the organisations as they actually operated: recurring losses, weak portfolio quality, fragmented control, expensive funding. The post-PMI view modelled what a successful integration could unlock — a replaced operating system, more effective funding, stronger cost control, a more disciplined sales model, and a redesigned organisational structure. The higher value was conditional, not automatic; it existed only on the far side of a well-executed integration.

Before any system went live, the acquired contract database was analysed in full. Every contract was recalculated using the pricing model already developed in Poland — financing, residual value, service, insurance and other assumptions, with local differences incorporated rather than ignored. This produced a clearer view of the portfolio's real economics, a validated and cleaned migration base, and visibility into contracts whose economics were weaker than locally reported.

The migration did not simply move old data forward. It moved data that had first been re-examined.

The data moved only after the economics behind it had been understood.

03

Three Markets in Two Weeks

The Polish operating system became the core, adapted to local currencies, taxes and market-specific rules. The Czech Republic and Slovakia — similar enough in tax and operating logic — were implemented together, in approximately four days. Hungary needed its own localisation and followed the next week. Across all three markets, the rollout took approximately two weeks, carried out in 2020 under COVID restrictions, combining frequent physical presence with continuous remote support.

A connected accounting environment went live in parallel: local charts of accounts mapped to the Polish, group and management-accounting structures, invoice layouts and local tax logic ready in time for the monthly cycle. By the invoicing date on the 20th, the acquired operations were issuing complete customer invoices from the new system.

Three markets migrated in two weeks. Full customer invoicing ran from the new system by the first billing cycle.

04

Stabilisation Before Optimisation

This was not a simultaneous, big-bang transformation. It was a fast installation of a stable core, followed by controlled, sequenced integration: secure the contract data and understand the portfolio; implement pricing, contract management, invoicing and accounting; keep local sales and operations running; connect the markets to the shared IT network; establish finance control and reporting; stabilise the relationship with local accounting providers — and only then optimise funding, cash management, cost structure and the wider operating model.

Stabilise what the business needs to survive. Optimise only when the system can absorb change.

05

From System Use to Organisational Ownership

Sales and operations stayed local. A colleague trained designated key users and supported them remotely; a member of Tomasz's team handled finance under his supervision; IT connected the acquired organisations to the shared network. Local headcount moved from roughly 15 people per market to somewhere around 10–12 — mainly duplicated finance and administrative roles no longer needed once responsibilities moved into the regional model, though the figure isn't a precise net saving, since some of that work was absorbed centrally rather than eliminated.

The local directors, designated as key users, resisted at first — they saw themselves as managers of people, not operators of a system, and putting that responsibility on a more junior specialist would have created real business-continuity risk in organisations this small. It took several visits and repeated explanation before the markets began sharing a common language and decision logic. In the early months, directors escalated many decisions upward and leaned heavily on the system specialist, which sometimes moved responsibility up rather than keeping it local.

Shared understanding could not fully precede the rollout. Tomasz built the necessary understanding first, through due diligence and portfolio recalculation; wider organisational shared understanding developed only after people could see and use the working system.

People could understand the system only after they could see the system working.

After approximately one year, the directors and their teams were managing pricing, processes and routine decisions with far less support, and the visits that once carried the integration became far less frequent.

The system went live in two weeks. Organisational ownership took a year.

06

Stopping the Leakage

The redesigned model built controls into the normal flow of work rather than adding them as separate checks: no vehicle could be ordered without a specific customer contract; customer-risk assessment tightened before a contract was accepted; local collections were strengthened so weak payment behaviour stopped being passively absorbed; service work moved to contracted repair networks with negotiated terms; insurance conditions were renegotiated, cutting costs meaningfully; and pricing and contract data ran through one consistent calculation logic instead of several local ones.

None of this could undo the value the inherited portfolio had already lost. What it could do — and did — was stop the same pattern from repeating.

The inherited stock confirmed the valuation. The redesigned operating model reversed the trend.

07

The Three Clocks of Integration

The due-diligence read on the inherited portfolio turned out to be substantially correct, and much of the expected transaction upside was absorbed by losses on non-earning vehicles that had been sitting in stock without contracts. The integration could not recover value the old portfolio had already destroyed. It could clean the portfolio and stop the pattern continuing.

New business began developing more consistently once the inherited stock was substantially addressed, and the customer base shifted from opportunistic transactions toward real, repeatable relationships. The first small profits appeared in 2021; by 2022, about two years after integration began in 2020, the businesses were producing a more satisfactory level of profit.

None of that arrived on the technical clock. Three separate clocks were running underneath the same integration, at three different speeds:

Technical integration took two weeks. Organisational ownership took a year. Economic integration took two years.

08

What This Case Later Revealed

Read today, this case connects to elements later named through Adaptive Thinking — vocabulary that didn't exist in 2020, applied here as a mapping, not a claim that the method was consciously followed.

Preparing the Ground shows up before the rollout, not after it: the first shared reality came from re-examining the full contract base rather than accepting what had been inherited on paper. That understanding belonged to one person before it belonged to the organisation — wider shared understanding only followed, once people had a working system to point to and explain from.

The Adaptive Spiral shows up in the sequence itself — diagnose, stabilise, observe, transfer capability, correct, optimise — with local anomalies absorbed into the model as they surfaced rather than designed away in advance.

Embedded Governance is visible in contract-linked vehicle ordering, risk assessment, collections and pricing logic built into daily operations rather than policed separately. The wider operating model kept sales and operations local while connecting finance, risk and control regionally.

Business System Architect describes the role rather than the title actually held. The work connected transaction logic, portfolio economics, systems, accounting, people, governance, funding and daily operations — and continued past go-live, deliberately, until responsibility had genuinely transferred into the organisation.

The PMI did not begin with a formal integration office. It began with someone holding the whole system together.

The honest limitation runs through the whole case: the fast rollout created real dependency, on Tomasz and on the system specialist, that took a year to unwind — a trade-off created by the speed of the initial stabilisation.

Fast integration is not the same as finished integration.

Evidence note

The acquired company is anonymised in this case, and the acquisition price and any discount to asset value are not disclosed. All figures below are approximate and based on professional recollection rather than a contemporaneous audit:

• Combined inherited portfolio: approximately EUR 30 million, roughly EUR 10 million per market.
• System rollout: Czech Republic and Slovakia together in approximately four days; Hungary the following week; approximately two weeks in total across all three markets.
• Local headcount: approximately 15 per market before, roughly 10–12 after — not a precise net saving, since some duplicated work moved to the regional team rather than disappearing.
• Timeline to organisational ownership: approximately one year. Timeline to a satisfactory profit level: approximately two years, from 2020 to 2022.

No precise profit or portfolio-loss figures are published here without supporting records. Performance after Tomasz Mazurkiewicz left the organisation is not attributed to him in this case, and the 2022 result should be read as a fact about the business, not a claim about anyone's individual result.

Formal role held: Deputy Regional CFO during the initial integration, Regional CFO from 2022. He was not a formally appointed PMI Director; the case describes what he did, not a title he held.