Brickstone https://staging.brickstone.africa An independent management consultancy. One measured outcome per engagement, published either way. Wed, 02 Sep 2026 09:00:00 +0000 en-US hourly 1 https://wordpress.org/?v=7.1.5 Agree the number before the work, or you will agree it after https://staging.brickstone.africa/insights/the-number-before-the-work/ Wed, 02 Sep 2026 09:00:00 +0000 https://staging.brickstone.africa/?p=3000 Brickstone

Agree the number before the work, or you will agree it after

Every argument about whether a programme succeeded is really an argument about a figure nobody wrote down in week one. Sixty-four engagements in, here is what writing it down does.

This post Agree the number before the work, or you will agree it after first appeared on Brickstone and is written by Taofeek Mashood

]]>
Brickstone

Agree the number before the work, or you will agree it after

In 2021 we made one rule for the firm: no engagement starts until the client and we have agreed, in writing, the single number it will be judged on. Not a set of objectives. Not a balanced scorecard. One figure, with its unit, its baseline and the date it will be read.

Five years and sixty-four engagements later the rule has cost us work, three prospective clients declined to name a number and went elsewhere, and it has produced the only honest scoreboard we know of in our industry. This piece is about what the rule actually does, day to day, and what it does not.

It ends the argument in week one instead of week forty

The typical transformation programme discovers in its last quarter that finance, the sponsor and the consultants have three different definitions of success. Each is defensible. None was written down. The programme is then judged on whichever definition the loudest person in the room holds, which is to say it is not judged at all.

Writing the number down moves that argument to week one, when it is cheap. It is not a pleasant week. In roughly a third of our audits the client’s first proposed number turns out to be unmeasurable with the data they have, and we spend a fortnight finding one that is.

19 of 64

audits whose first recommendation was not to hire us

How it was measured 

A rota change, a pricing correction, a conversation with a supplier. The rule makes these easier to say, because the number is already agreed and the honest route to it is often not a project.

It makes the boring stage fundable

Nobody puts data foundations in the press release. Nobody funds eight weeks of field definitions and lineage maps for their own sake. But once the number is written down (median hours from claim receipt to first decision, say) the question ‘can we currently measure that?’ has to be answered, and the answer is usually no. The boring stage becomes the obvious first step rather than a plea.

It publishes the failures

Two of our twelve published outcomes are smaller than the client hoped for. They are on the site because that is what publishing means. A firm that only shows the numbers it likes has a marketing page, not a record, and a board deciding whether to hire it deserves to know the difference.

The most valuable slide in the deck was the one that said which two product lines to stop.

Chief Executive, Fennimore Foods

What it does not do

  • It does not make the number move. Agreeing it is the start of the work, not a substitute for it.
  • It does not protect against a badly chosen number. We have twice agreed a figure that turned out to measure the wrong thing and had to renegotiate it mid-engagement, in writing, again.
  • It does not suit every buyer. A firm that wants a strategy without a scoreboard should hire someone else, and we say so.

If you are about to start a programme of any size, try it before you sign anything: one figure, one unit, one baseline, one date. If the room cannot agree, you have learned the most important thing about the programme before spending a pound on it.

This post Agree the number before the work, or you will agree it after first appeared on Brickstone and is written by Taofeek Mashood

]]>
The process map drawn in the meeting room is fiction https://staging.brickstone.africa/insights/measure-on-the-floor/ Wed, 26 Aug 2026 09:00:00 +0000 https://staging.brickstone.africa/?p=3001 Brickstone

The process map drawn in the meeting room is fiction

Six weeks on the floor at a forty-depot network found that the documented process had eleven steps and the real one had nineteen. Every efficiency programme built on the eleven had failed.

This post The process map drawn in the meeting room is fiction first appeared on Brickstone and is written by Taofeek Mashood

]]>
Brickstone

The process map drawn in the meeting room is fiction

Ask a team to describe its process and you will get the process as designed. Ask the same team to describe last Tuesday and you will get something else, the workaround for the system that times out, the manual check that exists because of an incident in 2019, the handover that happens by phone because the form does not have the field.

We call the second thing the operation. It is the only one worth redesigning, and it can only be found by watching.

What six weeks on the floor finds

At a logistics network last year the documented inbound process had eleven steps. Measured at the depot, it had nineteen: three re-keys of the same consignment number, two waits for a supervisor, one walk to a printer at the other end of the building. Two previous efficiency programmes had redesigned the eleven and delivered slides.

19 vs 11

steps in the real inbound process against the documented one

How it was measured 

Measured across four depots over six weeks. The eight undocumented steps accounted for 34% of handling time.

Why it has to be measured, not asked

People do not hide the workarounds. They do not see them. A re-key that has happened every day for three years is not a step; it is the job. The only way to find it is to sit beside the work with a stopwatch and a notebook and count.

This is expensive, six weeks of two people, and it is the cheapest part of any operations engagement, because everything designed afterwards is designed against the truth.

What to do with the nineteen

  • Redesign with the team leads in the room, not with the process owners. The team leads know why step fourteen exists.
  • Test in one depot, one queue or one shift before asking the rest to change. A redesign that survives one site earns the right to the others.
  • Publish the weekly run-rate inside the firm for a year. A saving that lives only in a business case is not a saving.

This post The process map drawn in the meeting room is fiction first appeared on Brickstone and is written by Taofeek Mashood

]]>
Against the pilot https://staging.brickstone.africa/insights/against-the-pilot/ Fri, 14 Aug 2026 09:00:00 +0000 https://staging.brickstone.africa/?p=3002 Brickstone

Against the pilot

A pilot answers “can this work?”, which is rarely the question. The question is “will we run it?”, and a pilot is designed to avoid answering that.

This post Against the pilot first appeared on Brickstone and is written by Taofeek Mashood

]]>
Brickstone

Against the pilot

Pilots are popular because they are safe. Nobody was ever fired for running one. They are also, in our experience, the most reliable way to spend a year proving something everybody already believed and then not doing it.

What a pilot proves

That the idea works under conditions chosen to make it work: the friendliest team, the cleanest data, the most patient sponsor. This is not nothing, but it is rarely the thing anyone doubted.

What a pilot avoids

Who owns it afterwards. What the evaluation threshold is. What happens when the friendly team is replaced by the one that has three other priorities. Whether IT will approve it. Whether the data is like this everywhere. Every one of these questions is deferred to ‘after the pilot’, and after the pilot the budget is spent.

4 of 5

abandoned systems we have reviewed that were technically fine

How it was measured 

They died in the handover, nobody owned the thresholds after the consultants left. None of them died in the pilot.

What to run instead

A thin slice: one job, end to end, in production, in the real environment, with the real access controls and an owner named before it starts. It is slower to launch than a pilot and faster to be real. If it survives one queue it earns the next; if it does not, you have learned something a pilot could not have told you.

A demo takes a fortnight. A system your staff rely on at nine on a Monday takes twelve weeks.

Marek Halloran, founding partner

This post Against the pilot first appeared on Brickstone and is written by Taofeek Mashood

]]>
Your management pack cannot show you where the margin goes https://staging.brickstone.africa/insights/the-margin-map/ Fri, 31 Jul 2026 09:00:00 +0000 https://staging.brickstone.africa/?p=3003 Brickstone

Your management pack cannot show you where the margin goes

It is organised by category, and margin does not live in categories. It lives in products, stores and baskets. Rebuilding it from the ledger found that a fifth of a retailer's range was paying for the rest.

This post Your management pack cannot show you where the margin goes first appeared on Brickstone and is written by Taofeek Mashood

]]>
Brickstone

Your management pack cannot show you where the margin goes

A management pack is a set of answers to the questions the business asked when the pack was designed. When the question changes (why is revenue up and margin down?) the pack has no page for it, and the meeting turns into a set of category managers each explaining why it is not their category.

Rebuilding margin from the ledger

We start from the general ledger and the transaction log, not the pack, and rebuild contribution three ways: by product after supply-chain cost, by store after labour and property, by basket after promotion. It takes three weeks and it always surprises someone.

1 in 5

products at a 240-store retailer contributing nothing after supply-chain cost

How it was measured 

The pack showed every category profitable. The ledger showed a fifth of the range paying for the rest. Two ranges were exited; gross margin rose 3.4 points on flat revenue.

Why nobody had seen it

Because the pack allocated supply-chain cost by revenue share, which flatters low-margin, high-volume lines. Because promotions were reported by the marketing team against a different period. Because the store-level labour cost sat in a different system. None of this was wrong. It simply could not be asked the question.

What to do with the map

  • Mark every line grow, hold, fix or exit, one of four, written down, with the number.
  • Test any price change in a dozen stores for eight weeks before asking the estate.
  • Build the function that keeps the map true. A margin map is wrong within a year; a pricing team is not.

This post Your management pack cannot show you where the margin goes first appeared on Brickstone and is written by Taofeek Mashood

]]>
What a new regulation actually asks of a mid-size firm, in numbers https://staging.brickstone.africa/insights/what-the-regulation-asks-in-numbers/ Fri, 17 Jul 2026 09:00:00 +0000 https://staging.brickstone.africa/?p=3004 Brickstone

What a new regulation actually asks of a mid-size firm, in numbers

Not the legal summary, which exists everywhere. The count of systems a 400-person insurer had to classify, how long each tier took, and which obligations turned out to be cheap.

This post What a new regulation actually asks of a mid-size firm, in numbers first appeared on Brickstone and is written by Taofeek Mashood

]]>
Brickstone

What a new regulation actually asks of a mid-size firm, in numbers

Every regulation arrives with a thousand summaries and no numbers. This is the numbers version, from one readiness engagement at a 400-person insurer in scope for the EU AI Act, written so that a risk team elsewhere can budget rather than worry.

The inventory

61

systems that made an automated or assisted decision about a person

How it was measured 

The firm's own estimate before the inventory was 'about fifteen'. The rest were spreadsheets, vendor tools and a pricing model nobody had thought of as AI.

The inventory took three weeks and was the most valuable artefact of the engagement. Most of the sixty-one were out of scope or minimal-risk; knowing which was the whole job.

The tiers

  • 44 minimal risk, a register entry and an owner. Half a day each.
  • 13 limited risk: transparency obligations. Two days each, mostly writing the notice.
  • 4 high risk: the full set: risk management, data governance, logging, human oversight, conformity. Six to nine weeks each, and the whole budget.

What was cheap

Transparency. Logging, where the system already had audit trails. Human oversight, where a person already reviewed the output: the obligation was to write down what was already happening. Roughly 70% of the obligations were met by documenting existing service properly.

What was not

Data governance for the four high-risk systems. In every case the training data’s lineage lived in somebody’s head, and reconstructing it was the long pole. This is not a regulatory cost; it is a debt the regulation made visible.

The register is now maintained by two people who do not work for us. That was the test.

Ines Duarte, partner

This post What a new regulation actually asks of a mid-size firm, in numbers first appeared on Brickstone and is written by Taofeek Mashood

]]>
Integrate by what the customer notices, and do the org chart last https://staging.brickstone.africa/insights/integrate-by-what-the-customer-notices/ Fri, 03 Jul 2026 09:00:00 +0000 https://staging.brickstone.africa/?p=3005 Brickstone

Integrate by what the customer notices, and do the org chart last

Most post-merger integrations start with the organisation because it is the thing the leadership team can see. The customer cannot see it, and the synergy case does not move until they can.

This post Integrate by what the customer notices, and do the org chart last first appeared on Brickstone and is written by Taofeek Mashood

]]>
Brickstone

Integrate by what the customer notices, and do the org chart last

A year after a deal closes, a surprising number of acquired businesses still run two of everything: two sales teams with two rate cards, two platforms, two finance systems. The org chart, meanwhile, was integrated in month two: because the org chart is the one thing the leadership team can see from where it sits.

Sequence by visibility to the customer

We set the order of an integration by one question: what will the customer notice first? One sales conversation and one rate card, usually. Then one platform. Then one invoice. The organisation follows the work, not the other way round, and the synergy case starts moving in month two instead of month fourteen.

9 months

two publishers to one operating model

How it was measured 

Twelve milestones agreed in week one; the synergy case delivered at 104% of plan. The group's previous integration took three years and was never declared finished.

One plan, one register, one report

Integrations die of parallel plans. Each workstream keeps its own, each reports green, and the programme discovers in month nine that the platform migration assumed a data model the finance workstream had already retired. One plan, one risk register, one monthly report to the board and one weekly report inside the firm, and a programme director with the authority to stop a workstream.

Hand the office over by month six

A programme office run by consultants for two years is a consultancy with a badge. Ours is built to be handed to the client’s finance function by month six, and the fee schedule says so.

This post Integrate by what the customer notices, and do the org chart last first appeared on Brickstone and is written by Taofeek Mashood

]]>
The savings programme that reports status and decides nothing https://staging.brickstone.africa/insights/the-savings-programme-that-decides-nothing/ Fri, 19 Jun 2026 09:00:00 +0000 https://staging.brickstone.africa/?p=3006 Brickstone

The savings programme that reports status and decides nothing

A council eleven months from a section 114 notice had run three savings programmes. All three had reported monthly. None had been able to say no to a directorate.

This post The savings programme that reports status and decides nothing first appeared on Brickstone and is written by Taofeek Mashood

]]>
Brickstone

The savings programme that reports status and decides nothing

The public sector runs more transformation programmes per pound than any other, and most of them share a design flaw: the programme office reports and the directorates decide. When a directorate’s saving slips, the office records the slip. Nobody in the structure is able to say ‘no, this happens’.

Give the programme a director who can stop a workstream

At a council facing a section 114 notice we did three things in week one: agreed the number (£6.2m recurring) with the chief executive and the section 151 officer, appointed a programme director with written authority to stop or resequence any workstream, and published weekly cash to every head of service.

£6.2m

recurring savings, budget balanced in-year, no service closed

How it was measured 

Recognised in the audited outturn against the baseline agreed in week one. The programme office is now run by the council's own finance team.

Sequence by what residents notice last

Back-office consolidation, procurement, property, then service redesign, in that order, because residents notice the last first. Three of the four previous programmes had started with the service redesign, which is where the resistance is, and stalled.

Publish inside, not just up

The board saw a monthly report. Every head of service saw the weekly cash position and every other directorate’s progress. Peer visibility did more for delivery than any escalation route.

This post The savings programme that reports status and decides nothing first appeared on Brickstone and is written by Taofeek Mashood

]]>
Brickstone Capital Flow Reports Jan-Apr 2026 (Issue 03) https://staging.brickstone.africa/insights/brickstone-capital-flow-reports-jan-apr-2026-issue-03/ Wed, 10 Jun 2026 22:12:56 +0000 https://staging.brickstone.africa/?p=18515 Brickstone

Brickstone Capital Flow Reports Jan-Apr 2026 (Issue 03)

Executive Summary Nigeria’s external capital account opened in 2026 with a surge of extraordinary scale. Total capital inflows reached USD 3.52 billion in January 2026, representing a 181.6% month-on-month acceleration from December…

This post Brickstone Capital Flow Reports Jan-Apr 2026 (Issue 03) first appeared on Brickstone and is written by Brickstone Editor

]]>
Brickstone

Brickstone Capital Flow Reports Jan-Apr 2026 (Issue 03)

Executive Summary

Nigeria’s external capital account opened in 2026 with a surge of extraordinary scale. Total capital inflows reached
USD 3.52 billion in January 2026, representing a 181.6% month-on-month acceleration from December 2025
baseline, the single largest monthly inflow volume recorded in the current monetary tightening cycle.1 This peak was
driven entirely by portfolio capital responding to the extraordinary real yield advantage embedded in the Nigerian
fixed-income market following the 2024 NBS CPI rebasing exercise, which reset the measured inflation trajectory to
a structurally lower level and, in doing so, pushed real policy rates firmly into positive territory for foreign investors.

The composition of these inflows, however, reinforces a structural vulnerability that has consistently flagged across
this series: 95.72% of January’s USD 3.52 billion consisted of portfolio investment, including short-term, yield-chasing
capital deployed principally into Treasury Bills and OMO instruments.2 Foreign Direct Investment, the
durable capital that finances productive capacity, contributed a mere USD 0.03 billion, or 0.77% of total inflows. This
is not a flow structure that builds an economy. It is a flow structure that can, under adverse global conditions,
reverse with the same speed and violence with which it arrived.

The period under review closes with a more cautionary signal. By April 2026, external reserves had declined by
USD 731 million, from USD 49.18 billion in March to USD 48.45 billion, reflecting a consolidation phase marked by
portfolio outflows triggered by mild global risk-off positioning.3 The reserve buffer remains substantial, and the CBN’s
ability to manage orderly FX conditions is not in question at current reserve levels. However, the trajectory
reinforces the fundamental asymmetry of Nigeria’s current capital account: inflows arrive in concentrated bursts tied
to yield dynamics; outflows, when they occur, are systematic and indiscriminate.

 

Fill the form below to download

Let’s make Infrastructure Happen! Learn more about the Brickstone Infrastructure Acceleration Programme here.

This post Brickstone Capital Flow Reports Jan-Apr 2026 (Issue 03) first appeared on Brickstone and is written by Brickstone Editor

]]>
Copilots fail in the handover, not the model https://staging.brickstone.africa/insights/copilots-fail-in-the-handover/ Fri, 05 Jun 2026 09:00:00 +0000 https://staging.brickstone.africa/?p=3007 Brickstone

Copilots fail in the handover, not the model

Four of the five systems we have seen abandoned were technically fine. They died because nobody owned the evaluation thresholds after the consultants left.

This post Copilots fail in the handover, not the model first appeared on Brickstone and is written by Taofeek Mashood

]]>
Brickstone

Copilots fail in the handover, not the model

We are sometimes asked to review a system a previous firm built and a client stopped using. We have done five. In four, the model was fine: accuracy within a point of launch, latency acceptable, no incident. What had failed was everything around it.

What actually broke

  • Nobody owned the evaluation threshold. When the model’s accuracy drifted two points, nobody knew whether that mattered, so somebody turned it off.
  • The training data’s lineage lived with an engineer who left.
  • The runbook was a slide deck. The first incident at 3am was handled by turning the system off, and it stayed off.
  • The people who had built it with the consultants had been moved to the next project.

4 of 5

abandoned systems that were technically fine

How it was measured 

Reviewed 2023–2026 across three sectors. The fifth had a genuine data problem, which the handover would also have caught.

What a real handover contains

An operating model with a named owner for the threshold and a named owner for the data. A runbook written by the client’s team, with us reading over their shoulder. A rehearsal: twice, and the second time the consultants say nothing. And a date after which the invoice stops, agreed before the build starts.

The measure of the handover is our own absence.

Tobias Lindqvist, partner

This post Copilots fail in the handover, not the model first appeared on Brickstone and is written by Taofeek Mashood

]]>
The builds we argued against, and what happened instead https://staging.brickstone.africa/insights/the-builds-we-argued-against/ Fri, 22 May 2026 09:00:00 +0000 https://staging.brickstone.africa/?p=3008 Brickstone

The builds we argued against, and what happened instead

Nineteen of sixty-four audits ended with a first recommendation we do not sell, a rota change, a pricing correction, a conversation with a supplier. Three of them, in detail.

This post The builds we argued against, and what happened instead first appeared on Brickstone and is written by Taofeek Mashood

]]>
Brickstone

The builds we argued against, and what happened instead

The audit is designed so that its first recommendation can be ‘not us’. It has been, nineteen times. Here are three, because a firm that only publishes the engagements it won has published a sales page.

The energy company that wanted three programmes

After a maintenance redesign had gone well, the board wanted to repeat it everywhere at once. The audit priced all three and argued against two: one because the sensor data could not carry it, one because a rota change achieved most of the benefit for none of the cost. €4.1m of maintenance capacity came back from the one that survived. The rota change was implemented by the client in a month.

The retailer that wanted a forecasting model

Stock-outs were the symptom. The audit found the replenishment rule was fine and the supplier’s lead time was quoted in working days while the system assumed calendar days. One conversation with the supplier. No model.

The lender that wanted a data platform

Two reports disagreed. The proposed fix was a lake. The audit found the two reports defined ‘customer’ differently and had done since a 2017 migration. One definition, one owner, eight weeks of foundations. No lake.

19 of 64

audits whose first recommendation was something we do not sell

How it was measured 

Eleven of the nineteen later bought a second engagement. Eight did not, and were right not to.

The audit costs a fixed fee and four weeks. If it saves a board a programme it did not need, it was the best money in the year; if it finds one it does, the roadmap prices it. Either way the recommendation was written before anybody at Tessel knew whether it would lead to more work, which is the only reason it means anything.

This post The builds we argued against, and what happened instead first appeared on Brickstone and is written by Taofeek Mashood

]]>