Four days away. Nothing failed. The difficult decisions waited for you.
A test for working out which of your operational problems is holding the others in place, and which ones you could leave alone for a year without much changing.
You prepared for it. You told people who owns what, you made yourself available for anything genuinely urgent, and nothing broke while you were gone.
You came back to a stack of decisions that had been kept for you. Not one of them was an emergency.
You already know the business has operational friction. That is not the missing piece. The missing piece is knowing which of the problems you can name is the one holding the others in place.
This is a ten-page test for that. You take three recurring problems you already recognise, examine each against five criteria with the evidence written down, and finish with a provisional reading for each: which may deserve investigation, which may be left alone, or where you do not yet hold the evidence to say. And one thing to start this week.
It can help you examine problems you already recognise. It cannot identify constraints you have not noticed, or tell you whether your team would describe the same workflow the same way. Those need more than one account of the same work.
About twenty to thirty minutes in one sitting, then a short record you keep over the next three times the problem occurs. Nothing to book.
Is It a Bottleneck or Just an Irritation? arrives by email straight away, followed by four short emails over the next fortnight on diagnosing recurring operational problems. You can unsubscribe from those at any time, and the test is yours either way.
Privacy policy
I am Claire Beaumont. I spent eleven years inside service businesses dealing with the operating consequences of growth: delivery pressure, commercial exceptions, unclear handovers, and decisions that kept returning to the same few people. I now run Beaumont Operations, a new practice offering short diagnostic engagements for founder-led service businesses.
I understand what happens after a decision leaves the founder's office and enters the organisation.
Trois semaines d'août. Rien n'a cassé. Les décisions difficiles attendaient votre retour.
Un test pour repérer lequel de vos problèmes d'organisation pourrait entretenir les autres, et lesquels vous pourriez laisser tels quels pendant un an sans grande conséquence.
Vous aviez préparé votre départ. Vous aviez dit qui décidait de quoi, vous restiez joignable en cas d'urgence réelle, et rien n'a cassé pendant votre absence.
À la rentrée, vous avez retrouvé une pile de décisions qu'on avait gardées pour vous. Aucune n'était une urgence.
Vous savez déjà que l'organisation grince. Ce n'est pas ce qui manque. Ce qui manque, c'est de savoir lequel des problèmes que vous savez nommer pourrait entretenir les autres.
C'est un test de dix pages pour ça. Vous prenez trois problèmes d'organisation récurrents que vous identifiez déjà, vous les examinez selon cinq critères en notant chaque fois sur quoi vous vous appuyez, et vous repartez avec une lecture provisoire pour chacun : ce qui mériterait peut-être d'être creusé, ce qui pourrait être laissé de côté, ou ce sur quoi vous n'avez pas encore de quoi trancher. Plus une chose à commencer cette semaine.
Ce test vous aide à examiner des problèmes que vous identifiez déjà. Il ne peut pas repérer les contraintes que vous n'avez pas vues, ni vous dire si votre équipe décrirait le même processus de la même façon. Pour cela, il faut plus d'un point de vue sur le même travail.
Comptez environ vingt à trente minutes pour les huit premières pages, en une fois. La neuvième se remplit ensuite, au fil des trois prochaines fois où le problème se présente. Rien à réserver.
Une précision avant de vous inscrire : le test et les quatre e-mails courts qui le suivent sont en anglais. Le test s'intitule Is It a Bottleneck or Just an Irritation?, autrement dit : vrai blocage, ou simple agacement ?
Le test arrive aussitôt par e-mail, suivi sur une quinzaine de jours de quatre e-mails courts sur les problèmes d'organisation récurrents, l'ensemble en anglais. Vous pouvez vous désinscrire de ces e-mails à tout moment ; le test vous reste dans tous les cas.
Politique de confidentialité
Je m'appelle Claire Beaumont. J'ai passé onze ans au sein d'entreprises de services, à gérer les conséquences opérationnelles de la croissance : la pression des délais, les exceptions commerciales, les transmissions incomplètes, et des décisions qui revenaient sans cesse vers les mêmes personnes. Je dirige aujourd'hui Beaumont Operations, un cabinet récent qui propose des diagnostics courts aux entreprises de services dirigées par leur fondateur.
Ce que je comprends, c'est ce qui arrive à une décision une fois qu'elle quitte le bureau du dirigeant et entre dans l'organisation.
Day 0Mail
Your copy of the test
CB
Claire BeaumontBeaumont Operations · to you · Day 0
Inbox preview
The order matters more than finishing in one sitting
Here it is.
Attached, and downloadable here:
Two notes before you start.
First, give the evidence lines time. Pages 1 to 8 take about twenty to thirty minutes, but you can pause and come back. Keep the order: choose your three on page 2, complete the cards on pages 3 to 5, then use page 6 to consider whether they could share a cause. Pages 7 and 8 help you compare and read those answers.
Second, page 9 happens afterwards. You record the next three occasions when your chosen problem occurs. That may take longer than the fortnight of emails that follows; there is nothing to finish before the next one arrives.
I will send four short emails over that fortnight. If you would rather not have them, the link at the bottom removes you, and the test stays yours.
Claire
Claire Beaumont · Beaumont Operations · Lyon
You are receiving this because you asked for Is It a Bottleneck or Just an Irritation? on the Beaumont Operations website. Unsubscribe from the follow-up emails · Privacy policy
It improved for three weeks
CB
Claire BeaumontBeaumont Operations · to you · Day 2
Inbox preview
Then it faded, and nobody could say why
Perhaps you have fixed this before.
A tool is bought, the process is documented, or someone is hired to own it. For the first few weeks everyone is building the new arrangement, and things visibly improve. A few months later, the senior people are keeping their own notes because they do not trust what is in the platform, and updates are still being requested in the team chat because it is faster.
If any of that is familiar, the most useful thing to know about it is what it does not prove.
It does not prove that the team failed to adopt it, or that the wrong tool was chosen. The software may have been perfectly capable. It may have been asked to settle decisions the business had never made.
A project platform can make work visible, enforce fields and flag what is overdue. It cannot decide who is allowed to disappoint a client, when a custom request is commercially sensible, which promise takes priority, or how much risk a team lead may accept. Once those decisions exist, it can record them. It cannot make them on anyone's behalf.
Early gains can fade for several reasons. One worth examining is whether the tool was asked to settle a decision that still had no answer.
So the question worth asking about anything that did not hold is what it was meant to fix, and whether anyone had established what kind of problem that was.
For a problem you have in mind, think of one response you have already tried. What was it meant to change? If you are using the checklist, that is a question to keep beside the relevant card, to examine against the examples you record.
Claire
Claire Beaumont · Beaumont Operations · Lyon
You are receiving this because you asked for Is It a Bottleneck or Just an Irritation? on the Beaumont Operations website. Unsubscribe · Privacy policy
Has authority actually moved?
CB
Claire BeaumontBeaumont Operations · to you · Day 5
Inbox preview
Or only responsibility
An operations hire can inherit an impossible arrangement.
The founder concludes the person was not strategic enough. The person concludes they were given accountability without authority. Both are describing the same arrangement from opposite ends, and both can be largely right.
Here is one way it happens. The role is defined as owning operations. Commercial promises are still made without them, exceptions are still approved around them, and when a process holds up something important, it is overridden. The team learns that going to the founder produces a faster answer, and sometimes a more favourable one. Within a few months the job can become chasing information and repairing decisions, with little room left for shaping how work happens.
The arrangement can persist even when each person has a defensible reason for what they do. An override may protect a client. A shortcut may get an urgent answer. The founder may hold context the role has not been given.
In that arrangement, someone can be responsible for an outcome while the decisions that shape it remain elsewhere.
The test is not whether someone has been made responsible for something. It is whether they can reach a conclusion you would not have reached, and have it stand.
If a name repeats in the dependency lines, start there: what can that person decide, and does the decision stand?
Claire
Claire Beaumont · Beaumont Operations · Lyon
You are receiving this because you asked for Is It a Bottleneck or Just an Irritation? on the Beaumont Operations website. Unsubscribe · Privacy policy
You may not need a new process
CB
Claire BeaumontBeaumont Operations · to you · Day 9
Inbox preview
Some things are supposed to be irritating
It is easy to assume that a recurring problem needs a response: a new process, a new tool, a clearer document, another standing meeting.
Some do. A service business also runs on judgement, negotiation and exceptions, and some friction comes with that work. The objective was never to remove variation. It was to stop variation arriving by accident in places where it costs you.
Which means some of what is on your list can be left alone, as a decision you have made and can revisit.
A file naming convention that annoys everyone may be worth twenty minutes one afternoon without changing how work moves. A meeting that runs long can be imperfect without driving delivery failure. Where that is what the evidence shows, fixing either will feel productive, and the week afterwards may look much the same.
The harder version is that one or two things on your list may not need solving at all. Perhaps an exception you keep accommodating could stop being offered. Perhaps a service variation behind repeated rework could be narrowed. Perhaps a low-consequence inconsistency can stay inconsistent.
Stopping a troublesome exception can remove work at its source. The change still has to be explained and held to. Compare that with adding a step, tool or meeting that someone will need to maintain: ask what work each option removes, as well as what it adds.
If one of your three reached Worth improving when convenient, you have a reason to consider leaving it alone. Costly on its own calls for a decision about cost and risk, even when no wider effect is apparent.
Claire
Claire Beaumont · Beaumont Operations · Lyon
You are receiving this because you asked for Is It a Bottleneck or Just an Irritation? on the Beaumont Operations website. Unsubscribe · Privacy policy
What the test could not do
CB
Claire BeaumontBeaumont Operations · to you · Day 13
Inbox preview
And the three things you can do about it
The checklist works from your account of the business. That is its limit, and it is worth being specific about what sits outside it.
It cannot tell you whether your team would describe the same workflow the same way. It cannot show you where the written process stops matching what people do when something important is at stake. Your account alone may not show what happens to a problem when you are not available. And it cannot tell you whether the thing you already tried failed for the reason you think it did.
Examining those questions means comparing your account with documents, recent examples and the people involved.
That comparison is at the centre of the diagnostic engagement. Over twelve working days I interview you, review your documents, map one core workflow from beginning to end, and speak with up to three people in the business. I then compare what the process says, what people believe happens, and what happened in recent examples. The test uses five criteria from that work. The diagnostic adds cause and response history, examined against the map, the documents and the other accounts.
The output is up to three priority bottlenecks, and fewer if the evidence supports fewer. For each: the evidence behind it, what has already been tried and why it did not hold, and the structural change it requires. Then a sequenced ninety-day plan.
You may recognise some of the findings. I am not charging you to be surprised. What I am responsible for is showing whether the problems you already know about are connected, which deserve priority, what evidence supports that, and what should happen next.
Three things you can consider from here, even if page 9 is still in progress.
Gather the three instances from page 9 and decide for yourself. Page 9 follows your chosen problem over its next three occurrences, so you may not have them yet. Some of these questions may resolve once you do.
Give a team lead or operations manager a blank copy of one assessment page and ask them to answer criterion 3, dependency, on their own, before you compare notes. Where your answers diverge can be more informative than where they agree.
Or have it examined properly. €4,850 excluding VAT, twelve working days, and it does not include rollout, training or ongoing implementation management. You can implement the plan internally afterwards, engage me for one defined implementation project, or use the diagnosis to brief someone else.
That is the last of these. Thank you for reading them.
Claire
Claire Beaumont · Beaumont Operations · Lyon
You are receiving this because you asked for Is It a Bottleneck or Just an Irritation? on the Beaumont Operations website. Unsubscribe · Privacy policy
What to expect on Thursday 12 November 2026
CB
Claire BeaumontBeaumont Operations · to you · after booking
Inbox preview
Nothing to prepare, and one thing worth thinking about
Your call is booked for Thursday 12 November 2026 at 10:00 (Paris time, CET). Thirty minutes, by video.
Join the call · Add to calendar · Reschedule
Nothing to prepare, and nothing to send me in advance.
One thing worth having in mind: a recent occasion when work stopped and waited for a decision. What was needed, who could have made it, what happened instead. It gives us something specific to start from.
If you have used the diagnostic checklist, bring the three complaints you tested and where each one landed. If page 9 is under way, bring whatever instances you have so far.
If you have not used the checklist, that is fine. It is not a prerequisite, and the call works the same way. The one example above is enough.
What we will not do on this call is diagnose your operating problem. Thirty minutes of your account is not enough for that, and I would rather tell you what a proper diagnosis involves than guess at one.
If the diagnostic is not right for your situation, I will say so on the call. That is a normal outcome, not a wasted half hour.
If the time stops working, the reschedule link lets you choose another or cancel.
Claire
Claire Beaumont · Beaumont Operations · Lyon
You are receiving this because a thirty-minute call was booked with Beaumont Operations using this address. Privacy policy
Is It a Bottleneck or Just an Irritation?PDF
Page 1 of 10
PAGE 01 / 10
DIAGNOSTIC CHECKLIST
Is It a Bottleneck or Just an Irritation?
A practical test for deciding which operational problems deserve attention first.
Claire Beaumont · Beaumont Operations
You take four days away. You prepare for it: you tell people who owns what, and you stay reachable for anything genuinely urgent.
Nothing fails while you are gone. You come back to a stack of decisions that were kept for you, and not one of them was an emergency.
That stack is hard to read. There is no failure in it to point at. The work continued, clients were served, and the people you hired are capable. The ambiguous work waited, and it waited for you.
THE MISSING PIECE
You already know the business has operational friction. What is missing is knowing which of the problems you can name is holding the others in place, and which ones you could leave alone for a year without much changing.
WHAT THIS TEST DOES
You take three recurring problems you already recognise and examine each one against five criteria, writing down the evidence behind every answer. At the end you will have a provisional reading for each: which may deserve investigation, which may be left alone, or where you do not yet hold the evidence to say. You will also have one thing to start this week that does not involve hiring anyone.
WHAT IT CANNOT DO
This test works from one account of the business: yours. It can help you examine problems you already recognise. It cannot identify constraints you have not noticed, check your account against anyone else's, or establish what causes a problem. Those need evidence from more than one account of the same work.
Every reading you reach here is provisional: your own account, read carefully, at this point in time.
TIME
Pages 1 to 8 take about twenty to thirty minutes, in one sitting. Page 9 happens afterwards, over the next three times the problem occurs. Nothing to book.
PAGE 02 / 10
Choosing your three
Write down three recurring operational problems, in the words you would use with someone who already knows the business. Write them the way you would say them, before anyone tidies them into management language.
At this stage they might look like this:
Everything comes back to me.
Sales and delivery keep misunderstanding each other.
The process is there, and people work around it.
Those are fine. They are too broad to act on, which is the point. By page 9, at least one of your three will be narrow enough to observe.
TWO RULES BEFORE YOU CHOOSE
1. Choose problems you believe have happened more than once in the last three months. The cards will ask you to name the occasions, and may change that initial view. A single bad project can deserve attention, but one occurrence cannot establish a recurring pattern.
2. Do not choose on recency alone. The most recent escalation feels central because it is loud. Whether it is holding anything up is a separate question, and it is the question this test asks. You meet problems in the order they demand your attention. Their order of importance can be quite different.
Write the complaint in the same words. Tick one answer per criterion and complete the evidence line. Both Yes and No need a basis; use Cannot say where the information is missing.
1 · Recurrence
Can you identify at least two occasions in the last three months? Tick No if your evidence shows fewer than two, and Cannot say if you do not know.
Write the complaint in the same words. Tick one answer per criterion and complete the evidence line. Both Yes and No need a basis; use Cannot say where the information is missing.
1 · Recurrence
Can you identify at least two occasions in the last three months? Tick No if your evidence shows fewer than two, and Cannot say if you do not know.
Write the complaint in the same words. Tick one answer per criterion and complete the evidence line. Both Yes and No need a basis; use Cannot say where the information is missing.
1 · Recurrence
Can you identify at least two occasions in the last three months? Tick No if your evidence shows fewer than two, and Cannot say if you do not know.
Three completed cards give you three better-described problems. That is already useful. Before you compare them, ask one more question of all three together.
Look back across pages 3 to 5 before you go any further.
ONE · Read your three dependency lines. Is the same name in more than one of them?
☐ Yes · ☐ No · ☐ Cannot say from what I have
TWO · Read all your evidence lines together. Is the same decision being made, avoided or remade in more than one complaint?
☐ Yes · ☐ No · ☐ Cannot say from what I have
THREE · If one of the three disappeared tomorrow, would either of the others become smaller?
☐ Yes · ☐ No · ☐ Cannot say from what I have
A Yes gives you a possible connection to examine. The same person appearing twice does not, by itself, establish a shared cause. Your complaints might be one unresolved decision showing up in several places, or separate problems involving the same person.
That possibility is worth sitting with for a moment, because it would change what comes next. Separate problems may need separate responses. One decision showing up in three places gives you a possible common starting point, and a question about who is in a position to take it.
Your three may also be genuinely separate. Do not force a connection to make the exercise tidier. The question is worth asking; the answer is allowed to be no.
Hold whatever you have written here as a possibility. If you are not sure, leave it open. Page 9 gives you a way to look more closely.
PAGE 07 / 10
Comparison
Transfer your marks from pages 3 to 5: Y for Yes, N for No, ? for Cannot say. This page holds marks only. The evidence stays on the cards, and page 8 will send you back to it. Fill in the last row once you have worked through page 8.
Each reading below is a provisional self-reading: what your own account suggests at this stage. Work through the readings in order for each complaint, and stop at the first one that applies.
Leverage carries most of the weight. Recurrence and Consequence decide which way it points, and Reach and Dependency show how much of the business is involved.
BEFORE ANY READING: SERIOUS HARM
If you already know that a complaint is doing serious harm now, to a client, to someone in the team or to the business, deal with it now, whatever reading it reaches below. The reading still has a use: it records your current view of what else might change.
1 · NOT ENOUGH EVIDENCE YET
Use this reading if any of these is true:
Leverage is Cannot say.
Recurrence is Cannot say.
Two or more criteria are Cannot say.
Leverage is No, and any other criterion is Cannot say.
You may already have clear examples. At least one part of the reading still needs evidence: what repeats, what it costs, who it depends on or what else might change.
A No on Leverage concerns the apparent reach of a change. It does not say that a problem can wait. Before treating the effect as contained, check that the other evidence lines support the reading.
This is a reasonable place to be with a problem nobody has examined deliberately. Use page 9 to record what is missing from your account. The next step is to look more closely, without forcing an answer.
2 · NOT YET A PATTERN
Leverage is Yes and Recurrence is No.
On your account, changing this could reduce several problems, but by your own count it has not yet happened twice in the last three months. That makes it worth watching. A single occurrence cannot show whether the business is built in a way that produces it. Page 9 is how you find out whether it repeats.
3 · STRONGEST CANDIDATE FOR INVESTIGATION
Leverage is Yes and Recurrence is Yes.
On your account, this complaint recurs and may be holding others in place. It is a candidate for investigation. Reach shows where it appears, Dependency identifies whose decisions it returns to, and Consequence describes the cost.
If more than one complaint reaches this reading, go back to page 6: they may be the same decision showing up twice. If they still look separate, take the one with the most specific evidence lines to page 9.
One risk at this point is acting on a sound reading with the wrong kind of response, such as adding a tool where a decision is missing, or documenting a process that has not yet settled.
4 · COSTLY ON ITS OWN
Leverage is No and Consequence is Yes, with every other criterion answered.
Your evidence suggests a costly problem whose effects may be contained. Deal with it deliberately; how soon depends on the cost and risk. Keep the expected benefit specific to what the evidence supports.
5 · WORTH IMPROVING WHEN CONVENIENT
Leverage is No and Consequence is No, with every other criterion answered.
Your evidence suggests a limited consequence and no wider change from resolving it. It may be reasonable to improve it when convenient, or leave it alone on purpose. Keep an eye on it if circumstances change.
IF NOTHING REACHED READING 3
That is still a result. It may mean the thing making the business heavier than it should be is not on your list. It may mean none of the three is central, and the business has no single dominant constraint. Or it may mean you do not yet hold the evidence to tell those apart. Page 9 can help with the third possibility. The first two need more than one account of the business, which is where page 10 begins.
PAGE 09 / 10
What to start this week
Choose the strongest candidate from your three, or one that needs more evidence. Over its next three occurrences, record the date and five details. Fill in each column soon after it happens, while the details are still clear.
Instance 1
Instance 2
Instance 3
Date
Where the work stopped
What decision was needed
Who could have made it
What happened instead
What the delay or workaround produced
Three instances can sharpen your account of where work stops and what appears to be missing. A process may need redesigning, a decision may need taking, or the evidence may point somewhere else. Recording who could have made a decision helps identify a question to ask; it does not explain why the decision was not made.
WHILE YOU OBSERVE
Do not change the workflow while you are observing it. Record what normally happens before you introduce a new process or open a discussion about it. Otherwise you will be measuring your own intervention.
Unless it is doing serious harm. If the problem is causing real damage now, act first and record what you changed. Do not preserve a workflow that is hurting you in order to finish an exercise.
AFTER THE THIRD INSTANCE
Read across the three columns. The dates and the order of events are useful context, though a sequence on its own shows only that one thing happened before another.
What you now think is happening, and what would change your mind:
Three instances refine your own account. Establishing a cause, or learning how someone else would describe the same events, takes more than one account, and page 10 sets out how to get one.
PAGE 10 / 10
What you still do not know
This test worked from your account of the business. Four things it could not reach:
01 · Whether the team's account matches yours. Where the accounts differ is where the next questions are.
02 · Where the written process stops matching what people actually do. A written process covers the situations someone thought to write down, and those may not be the ones that create commercial risk.
03 · What happens to this problem when you are not available. Your account alone may not show it.
04 · Whether what you already tried failed for the reason you think it did. A new tool, a new hire or a documentation project that did not hold may have failed for a cause nobody examined afterwards.
THREE THINGS YOU CAN DO FROM HERE
1 · Do nothing yet. Gather the three instances.
This is a real option, and it needs nobody else. Three recorded occurrences may support your reading, change it or dissolve it.
2 · Take it internally.
What you have recorded is enough to open this conversation with a team lead or an operations manager. This step goes beyond the test you have completed, because it adds a second account. Before you compare notes, give them a blank copy of one assessment page and ask them to answer criterion 3, dependency, on their own. Theirs is a second account of the same work, and it carries information yours cannot. Where your answers diverge can be more informative than where they agree.
3 · Have it examined properly.
The 12-Day Operations Diagnostic examines one core workflow across several accounts of the business and reduces the field to no more than three evidenced priorities, with a sequenced ninety-day plan.
This test uses five criteria from that work. The paid diagnostic adds cause and response history, examined against the workflow map, documents and other accounts of the same work.
WHAT I EXAMINE · After an intake questionnaire and up to twelve documents, over twelve working days and remotely, I interview you, map one core workflow from beginning to end, and speak with up to three people in the business.
WHAT YOU LEAVE WITH · A report of twelve to eighteen pages setting out up to three priority bottlenecks, and fewer if the evidence supports fewer. For each: the evidence behind it, what has already been tried and why it did not hold, and the structural change it requires. A sequenced ninety-day plan. A section on what I examined and deliberately did not prioritise. A ninety-minute final session, and a sixty-minute review ninety days later that closes the engagement.
WHAT IT DOES NOT INCLUDE · Company-wide rollout, team training or ongoing implementation management.
WHAT HAPPENS AFTERWARDS · You can implement the plan internally, engage me for one defined implementation project, or use the diagnosis to brief someone else. The diagnostic is complete without a continuing engagement.
€4,850 excluding VAT. Fifty per cent to reserve the engagement, fifty per cent before the final session.
I begin no more than two diagnostic engagements in a month, because the analysis requires holding several accounts of the same business in mind at once, and that does not survive volume.
Some of what is on your list can be left alone on purpose. What matters is finding the few operating decisions that keep recreating the problems around them.
Beaumont Operations · The 12-Day Operations Diagnostic
Beaumont OperationsLyon
Twelve working days to find out which operational problems are actually holding the others in place
A diagnostic engagement for founder-led service businesses that have already tried the obvious fixes.
A client asks why something discussed during the sales conversation never appeared in the project plan. The project manager says it was not in the handover. You go looking through the team chat, email and your own notes to reconstruct what you actually said, three weeks ago, to someone you have known for four years.
It takes forty minutes. You find most of it. The work continues.
Then a quieter month arrives, with fewer projects and less pressure, and the same confusion is still there.
That is the part worth paying attention to. The quiet month is more revealing than the bad one. When the pressure falls and the confusion stays, pressure was not the whole explanation.
What the obvious fixes have in common
By the time you look for outside help, you may already have tried several plausible fixes. A project platform. An operations hire. A documentation effort. A weekly meeting created to catch the things that were falling through.
Some of those may have been good decisions. Some may have improved things for a month.
What they share is that each began with a solution category already selected. A tool assumes the work needs a better container. A documentation project assumes the problem is that things were never written down. A delegation framework assumes the problem is delegation.
So it is reasonable to examine the next proposal carefully. The risk is committing to a response before establishing what kind of problem it is meant to solve.
That is what this engagement is for. It establishes which problems deserve a response before anything is implemented.
What it is
The 12-Day Operations Diagnostic. Twelve working days, remote, one core workflow examined properly.
Before day one. You complete an intake questionnaire and send up to twelve documents that describe how the work is supposed to move. We agree one core workflow to examine, such as client delivery, resourcing, the sales-to-delivery handover or how exceptions get approved, and you name the people I may speak with.
Days 1 to 2. A ninety-minute interview with you. Where you believe the friction is, what repeats, what has already been tried, where decisions return to you. I am also listening for language that is too broad to diagnose, such as the team lacks ownership, we need better systems or everything comes back to me. Those may all be accurate. None of them yet tells anyone where the failure occurs. By the end, we have five to eight specific points of friction to investigate. Nothing has been diagnosed.
Days 3 to 5. I map the chosen workflow from beginning to end and speak with up to three people in the business, such as a delivery lead, someone close to sales, or someone in operations or finance. I ask them to walk me through recent work. Where did you wait for a decision? What happened the last time a client asked for something outside scope? Which decisions can you make without checking? Then I compare what the process says, what people believe happens, and what happened in the last few real examples. You receive a draft workflow map you can recognise and correct.
Days 6 to 7. Each candidate is tested against seven criteria:
Recurrence: does it happen repeatedly?
Reach: how far does it spread across projects, clients and people?
Dependency: does resolving it depend on one particular person?
Consequence: what does it cost in delay, rework, commercial risk or quality?
Cause: what does the evidence suggest keeps producing it?
Response history: what has already been tried, and why did it not last?
Leverage: would changing this point reduce other visible problems, or would its effect stay with this problem?
If you have used the free test, you will recognise five of these. The paid diagnostic also examines cause and response history against the workflow map, documents and other accounts.
This is where separate-looking problems can turn out to share a cause. A meeting problem, a delegation problem and a project-management problem can all be sustained by the same unresolved decision boundary. They can also be three separate problems. The evidence decides which, and a name that keeps appearing is a reason to look more closely.
Days 8 to 9. For each evidenced priority, what would have to change structurally. A decision leadership needs to take. An ownership boundary. Authority transferred with explicit limits. A commercial rule. A redesigned handover. The removal of an approval that no longer earns its place. Or work that should stop existing. We test the emerging recommendations together in a short working session, because a recommendation can be correct on paper and ignore a commercial reality I have misunderstood.
Days 10 to 12. The report, the plan and a ninety-minute final session. The first half of the session walks through the evidence and the conclusions. The second half deals with sequence, ownership, and where resistance is likely, including where a recommendation changes who decides, approves or steps in.
Day 90. A sixty-minute review session closes the engagement.
What you leave with
A diagnostic report of twelve to eighteen pages. A map of the workflow we examined. Up to three priority bottlenecks, each with the evidence behind it, what has already been tried, why that response did not hold, and the structural change required. A ninety-day sequence with named ownership. One implementation aid, where the first action genuinely needs one, such as a draft decision-rights table, a handover structure or an exception rule. It follows from the diagnosis and is shaped around the first action it supports.
And a section listing what I found and deliberately did not prioritise, so you can see what was set aside on purpose, and why.
What it will not do
It will not assume you need more process.
A specialist service business runs on judgement, negotiation and exceptions, and some friction comes with that work. Sometimes the right conclusion is that a particular exception should stop being offered, a service variation should be narrowed, or an inconsistency can be left alone. Each option is weighed on the work it would remove as well as the work it would add. A new step has to be maintained. Stopping an exception still has to be explained and held to.
It does not include company-wide rollout, team training or ongoing implementation management. It goes far enough to make each recommendation usable, by specifying the decision required, the people involved, the first action and the sequence. It stops there.
It will not produce conclusions I cannot support. If I cannot evidence something from what I found in the work, it does not appear in the report.
That is also why the engagement promises up to three priority bottlenecks. If the evidence supports two, the report contains two. Padding it to three would be the same failure as recommending a tool nobody needs.
Why this is difficult to do from inside
An operations manager or head of operations may be entirely capable of this work. Their attention is pulled by delivery responsibility: they keep the current arrangement running while trying to examine it. They also sit inside the authority structure they may need to question. If they conclude that the founder is still the hidden approval point, saying so becomes a negotiation with their employer.
You know the business better than I ever will. You also meet each problem in the order it demands your attention, and the loudest escalation this week is not reliably the one holding things up.
A fractional COO arrangement can be designed to continue into implementation. This diagnostic is deliberately separated from that commitment.
What this produces is a diagnosis that is not committed in advance to a tool, a framework, a hire or a continuing engagement. It can conclude that you need one clearer decision, one redesigned handover, more authority for a role that already exists, a small amount of documentation, or no new system at all.
Who I am
I am Claire Beaumont. I spent eleven years inside service businesses dealing with the operating consequences of growth: delivery pressure, commercial exceptions, unclear handovers, overloaded managers, and decisions that kept returning to the same few people.
I have not founded and run a service business with my own capital, reputation and payroll attached to every decision, and I would not blur that distinction. You understand the stakes better than I do.
What I understand is what happens after a decision leaves the founder's office and enters the organisation.
Beaumont Operations is three months old. I have no case studies to place beside the price, and I am not going to construct something that resembles one. What you can examine before deciding is how I think: what I look at, what I exclude, what the engagement covers, and the standard I will hold the conclusions to.
Two things you are probably thinking
“So I am paying for a report.”
The report is where the thinking is recorded. It is not the unit being priced.
What you are paying for is the reduction of a competing set of symptoms, opinions and proposed fixes into no more than three evidenced priorities, and knowing what to deliberately leave alone for now.
“What if you tell me things I already know?”
You may recognise some of it. I would be suspicious of a consultant who expected every observation to surprise you.
The question is whether the business already knows those things in a form it can act on. Knowing that handovers are inconsistent is different from knowing which missing information causes the rework, why it is absent, which commercial decision currently sits outside the handover, and who has to make it.
You may know all the symptoms individually and still not know whether they share a cause.
If it turns out your original diagnosis was substantially right, I will say so. I am not charging you to be surprised.
And if, by the end of the first five working days, I conclude that we are examining the wrong area, or that I cannot perform a responsible diagnosis with the access available, I will tell you before producing a report. We either correct the scope together or stop the engagement under the terms agreed at the outset.
Price and terms
€4,850 excluding VAT.
Fifty per cent to reserve the engagement, fifty per cent before the final session. There is no discount for paying in full at the start.
I considered pricing this lower, given that the practice is new. The scope does not support it. Reducing the number would mean fewer interviews, fewer examples examined, or a shorter list of observations. That would produce the generic exercise you may already be sceptical of. I would rather lose the engagement than price below the cost of doing the work properly.
I begin no more than two diagnostic engagements in a month. The analysis requires holding several accounts of the same business in mind at once, and that does not survive volume. If both starts in a month are taken, yours moves to a later month.
What happens on day thirteen
The report, the map, the recommendations and the plan are written for you to use without me. You should not discover in the final session that the work is unusable unless you immediately hire me again.
From there, you have three routes. Implement it internally, which is a legitimate and complete option, particularly if you have an operations manager or capable team leads. Or engage me for one defined implementation project on a single priority, with a specific change, named stakeholders, a defined output and an endpoint. Or use the diagnosis to brief someone else entirely.
The correct order is to diagnose the operating problem, determine what kind of response it requires, and then decide who is best placed to implement it. Sometimes that is you. Sometimes it may be me. Sometimes it is a hire.
Some problems can be left alone on purpose. What matters is finding the few operating decisions that keep recreating the problems around them.
Thirty minutes. I will ask what is recurring and what you have already tried. If the diagnostic is not the right thing for your situation, I will say so on the call.
Beaumont OperationsLyon
A thirty-minute conversation about what is recurring
Before you pick a time, here is what this call is and is not, so you can decide whether it is worth the half hour.
What I will ask. What keeps coming back. What you have already tried, and what happened. Where decisions wait for you. Whether you have a sense of which part of the business the friction sits in.
What I will not do. Diagnose anything. Thirty minutes of one person's account is not enough to tell you where your constraint is. I will not pretend otherwise.
What you will leave with. A straight answer about whether the diagnostic is the right thing for your situation. Sometimes it is not, and I will say so. Three situations where it may not fit:
Your involvement in decisions may suit the stage the business is at. A founder being closely involved is not, by itself, a structural problem.
You may already know what needs to change and need someone to carry it out. That is implementation work, which the diagnostic does not include.
The method needs access to your documents and to up to three people in the business. If that access is not possible, the diagnostic cannot be done responsibly.
If one of these applies, I will tell you on the call and, where I can, say what kind of help looks like a better fit.
Useful to have in mind. Nothing to prepare. One recent example where work stopped and waited for a decision. If you have used the checklist, the three complaints you tested and where each one landed. If you have not used it, the call works the same way, and the example is enough.
The practical part. Thirty minutes, by video. Nothing to send in advance, and no presentation. The confirmation email carries the call link, a calendar entry and a way to move the time if you need to.