Author: philcharles

  • Whose Bridge Was It?

    Whose Bridge Was It?

    Ralph Freeman calculated every member of the Sydney Harbour Bridge. The clientโ€™s chief engineer said in print that he hadnโ€™t designed it. What the fight teaches consultants about expertise, responsibility and credit.

    On the morning of 11 March 1929, Sydney commuters opened the Sydney Morning Herald on the ferries and found a long signed article on the history of the Harbour Bridgeโ€™s design. Beside it was a photograph of the author, with a caption the paper wrote itself:

    โ€œDesigner of the Sydney Harbour Bridge, who writes on page 11 on the history of its design.โ€

    A reader on the upper deck only had to lift his eyes to see what the caption meant. The two unfinished halves of the arch were reaching out over the water from each shore.

    The man in the photograph was Ralph Freeman, a consulting engineer from London. Twelve days later the same paper ran a report from the stateโ€™s chief engineer, John Bradfield, under a headline in capitals:

    โ€œMR. FREEMAN NOT THE DESIGNER.โ€

    Same newspaper, same month, opposite answers. Nearly a century on, the question still hasnโ€™t been settled. If you sell expertise for a living, itโ€™s the most useful argument in Australian engineering history.

    The consultant

    Freeman joined the London firm of Sir Douglas Fox and Partners in 1901, straight out of college. His first big job was helping design the steel arch over the Zambezi at Victoria Falls, finished in 1905. He became a partner in 1912 and senior partner in 1921.

    In the early 1920s his firm was consulting to the Cleveland Bridge and Engineering Company, the contractor that had built the Victoria Falls arch. Cleveland was preparing a tender for Sydney, and Freeman led the design work.

    Then, in 1923, Cleveland pulled out. Dorman Long of Middlesbrough took over the tender, and took Freeman and Clevelandโ€™s chief engineer, G C Imbault, with it. The drawings went on being worked in the same London office, by the same people, for a client who hadnโ€™t commissioned them.

    In No Second Attempt I put it like this: Dorman Long bought the answer.

    Dorman Long won the contract in March 1924 with a scheme its tender said was โ€œprepared by Mr. Ralph Freeman and Mr. G. C. Imbault.โ€ The company set up a design department in London and put Freeman in charge. He was never its employee. He was its consulting engineer, a man who could be found at another address when he wasnโ€™t in the room.

    Every chord, post and diagonal of the arch was calculated in that office. Each member had its own sheet of figures: the weight of the steel itself, the trains, the trams, the road traffic, the wind and the loads of erection, which in some members were the worst the bridge would ever see. The section was chosen from the worst case, the drawing came from the section, and the prints went out to the workshops in Sydney. Most of the men who drew the arch never saw the harbour it was built over.

    The clientโ€™s engineer

    Bradfield had spent most of his career arguing for a harbour crossing. He chose the arch, set the span and drew the outline. He wrote the specification the world tendered against, and he recommended Dorman Long. When Freemanโ€™s articles appeared, he answered in a typed report to the Minister:

    โ€œI am solely responsible for the specification and plans upon which tenders were called, which governs the design of the details of the bridge. I wrote every word in the specification.โ€

    He concluded that Freeman โ€œcan in no way be acclaimed as having conceived the Sydney Harbour Bridge or being its โ€˜designer.โ€™โ€

    The reply

    Freeman wrote back to the Herald on 25 March 1929, five years and a day after the contract was signed. His letter is one of the best pieces of professional argument Iโ€™ve read.

    The specification, he said, held an outline elevation of the arch and no design of any bridge. An outline elevation was no more the design of a bridge than a photograph of a liner was the design of a ship.

    Then he found the hole in Bradfieldโ€™s own words. Bradfield had written every word of the specification, and clause 30 was one of them:

    โ€œIt is to be expressly understood that the contractor undertakes the entire responsibility not only for the manufacture and construction of the bridge but also for the design, calculations, specifications, and plans furnished to or by him…โ€

    The state had handed the design responsibility to the contractor in its own contract. Freeman quoted it straight back.

    He also pointed out that Dorman Longโ€™s tender had named him and Imbault as the designers, that the claim had stood under a large picture of the bridge at the Wembley Exhibition in 1924 and in advertisements around the world, and that nobody had challenged it in five years. He said why he was fighting:

    โ€œIn justice to myself, my staff, and my profession I must do so.โ€

    Who won?

    Nobody, officially.

    The Herald called it โ€œa regrettable controversy.โ€ When the bridge opened in 1932, Dorman Long threatened legal action if a plaque named Bradfield alone as designer. The Heraldโ€™s opening-day supplement dodged the question by giving three men three titles: Bradfield prepared the general design and specifications, Freeman was consulting and designing engineer for the contractors, and Lawrence Ennis was director of construction. The New South Wales department said Bradfield. The Institution of Civil Engineers in London recorded Freeman. Both records still stand.

    The line I wrote in the book is the closest Iโ€™ll come to a verdict: each man was describing real work and calling it design.

    What consultants can take from this

    Most consultants wonโ€™t design a harbour bridge. All of us will hit some version of Freemanโ€™s problem: we do the expert work, someone elseโ€™s name goes on it, and the contract never said who gets the credit.

    1. Responsibility and credit are different things

    Clause 30 settled responsibility completely. If the arch had failed, the design would have been Dorman Longโ€™s problem, and so Freemanโ€™s. It said nothing about credit. Bradfield could own the idea in the public mind while the contractor owned the risk on paper.

    Your engagement letter probably works the same way. It defines scope, liability and fees, and itโ€™s silent on attribution. Fix that. Write in how your work will be credited: in the report, in the clientโ€™s publicity and in your own portfolio. It costs one paragraph, and itโ€™s far easier to agree before the work is famous.

    2. Make your claim early, in writing, and in public

    Freemanโ€™s strongest evidence wasnโ€™t his calculations. It was a sentence in a tender document, repeated under a picture at Wembley and never contradicted for five years. That was a documented, public, unchallenged claim, made before there was anything to fight about.

    If youโ€™re a subconsultant, the client may not know you exist. Get your name on the deliverable, in the tender and in the project record while the project is still dull. Once itโ€™s a landmark, everyone will remember doing it.

    3. Pick the right court

    Freeman took the fight to a daily newspaper while the arch was half built and the clientโ€™s chief engineer was in the same city. It got him a caption, a rebuttal in capitals and an editorial calling the whole thing regrettable. The public never settled it.

    The record that lasted was the one his peers kept. The profession argued it out in the Institutionโ€™s proceedings, in the same volumes as the calculations, and thatโ€™s where his name sits.

    Your reputation as a consultant lives with the people who hire consultants: other engineers, other firms, the next clientโ€™s technical lead. If you have to defend your work, do it where theyโ€™ll read it, with documents, and leave the newspaper to the client.

    4. Your expertise travels, so build it into your name

    When Cleveland Bridge dropped out, Freeman didnโ€™t lose the job. He walked across to Dorman Long with the work in his head and his team behind him. Thatโ€™s the consultantโ€™s advantage in one sentence: the client can change and the expertise goes with you.

    He built on it. In 1935 his firm designed the Birchenough Bridge in what is now Zimbabwe, often described as a smaller replica of Sydneyโ€™s arch. In 1938 Sir Douglas Fox and Partners became Freeman Fox and Partners. He was knighted in 1947, and his son went on to lead the firm and design the Humber Bridge.

    The argument over a single word didnโ€™t decide his career. The body of work did.

    Two shillings each

    One more detail, because it says something about the kind of consultant Freeman was.

    When the arch was locked in August 1930, Freeman gave every Dorman Long employee on the job an Australian florin, a two shilling coin. It went to the rivet gangs, the dogmen, the men at the cable drives, the workshop hands at Milsons Point and the masons at the Moruya quarry, men whose names went on no drawing. Some kept the coin in a drawer. One was worked into a brooch and inscribed to a Jim and an Emma.

    The man who fought for nine years to be called the designer also made sure the people who built it got something to remember it by. Claim your work, and credit the people who carried it out. The two go together.


    Has a client ever taken credit for your work? How did you handle it? Hit reply. I read every one.


    Ralph Freeman, John Bradfield and the authorship fight run right through my new book, No Second Attempt: The Men Who Built the Sydney Harbour Bridge Out Over Open Water and Closed It in a Single Night, 1923 to 1932. It lays out both sides of the argument from the original documents and leaves the verdict to you. It also tells how the arch was actually built, out over open water with nothing underneath, and closed in a single night. Iโ€™m a civil engineer and a consultant, and I went back to the record to tell it the way it actually happened.

    see more on “No Second Attempt”

  • A quick question is rarely quick

    A quick question is rarely quick

    โ€œCould I ask one quick question?โ€ is the natural predator of the consultantโ€™s carefully planned day.

    The question may take only ten minutes to answer. But that is rarely the full cost.

    First, you stop what you are doing and shift your attention to the clientโ€™s problem.

    Then you locate the relevant email, reopen the project files, check an assumption and work out what has changed since the last conversation.

    You provide the answer, perhaps with a short explanation to prevent misunderstanding.

    Then you return to your original task and try to remember where you were.

    The ten-minute question may have consumed 30 or 40 minutes. More importantly, it may have broken a block of concentrated work that cannot easily be reconstructed.

    This is invisible consulting work.

    It rarely appears in the programme, proposal or scope. It may not be recorded on a timesheet. But it consumes real capacity and disrupts the work the consultant has already promised to deliver.

    Technical consultants are particularly vulnerable because we want to be helpful. We know the answer, or we know how to find it, so responding immediately feels like good client service.

    Sometimes it is.

    But when every request is treated as urgent, the consultantโ€™s week becomes a collection of other peopleโ€™s priorities.

    Reliable consultants do not need to ignore clients. They need a clear way of managing access.

    That might include:

    • agreed response times
    • scheduled check-in calls
    • a shared list of non-urgent questions
    • defined channels for genuinely urgent matters
    • a clear process for requests outside the current scope

    Responsiveness is not the same as immediate availability.

    A reliable consultant protects enough focused time to provide the thoughtful answer the client is actually paying for.

    How many โ€œquick questionsโ€ entered your week without ever appearing in your plan?

    The Reliable Consultant, practical observations for technical professionals building independent consulting practices.

  • Your expertise is not yet an offer

    Your expertise is not yet an offer

    โ€œI have 25 years of experienceโ€ is credible.

    It is not a reason to hire you.

    Technical professionals often describe their consulting services by listing their qualifications, years of experience, specialist knowledge and previous projects.

    All of these establish credibility. But they do not constitute an offer.

    A client is rarely looking to purchase 25 years of experience. The client is trying to resolve a problem, make a difficult decision, reduce a risk or achieve a result.

    Your experience matters because it improves your ability to help them do that.

    This is the distinction between describing yourself and describing your value.

    โ€œI am a civil engineer with 25 years of experience in infrastructure planningโ€ tells the client who you are.

    โ€œI help government agencies turn complex infrastructure problems into clear, defensible investment decisionsโ€ tells the client why your expertise matters.

    A credible consulting offer should answer four questions:

    1. Who do you help?
    2. What problem do you help them solve?
    3. What result do you help them achieve?
    4. Why should they trust you to do it?

    Your qualifications and experience largely answer the fourth question. Many technical consultants stop there.

    That leaves prospective clients to work out the first three for themselves. Most will not.

    This does not mean squeezing everything you know into a narrow box. It means giving people a clear entry point into your expertise. Your experience is the foundation.

    Your offer connects that experience to a problem someone is prepared to pay to solve.

    Try completing this sentence: โ€œI help [type of client] address [specific problem] so they can [valuable result].โ€

    If that sentence is difficult to complete, you may have considerable expertise but not yet have a clear consulting offer.

    The Confident Consultant, practical observations for technical professionals building independent consulting practices.

  • The Most Expensive Mistake in Consulting

    The Most Expensive Mistake in Consulting

    The advice they ask for isn’t the advice they need

    What if the most expensive mistake in consulting isnโ€™t getting the answer wrong, but getting the question right on somebody elseโ€™s wrong problem?

    I saw this on an infrastructure assessment project I reviewed. The technically excellent consultant spent eight weeks conducting a detailed geotechnical analysis. In Week 10, the client reviewed the draft and said, โ€œThis isnโ€™t what we needed. We needed options analysis for three different foundation types, not a deep dive on one approach.โ€

    The consultant spent the next four weeks rebuilding the analysis from scratch. Forty hours of work, completely wasted. Why? Because in Week 0, no one had clarified what good looks like. The consultant had assumed. The client had assumed the consultant would ask.

    On a $100,000 project, thatโ€™s $20,000 of work that added zero value. On a fixed-price contract, thatโ€™s $20,000 of pure loss. On a time-and-materials project, thatโ€™s a very awkward conversation with a client who is now paying for work twice.

    Here is the uncomfortable part. The consultant did exactly what the brief asked. The work was competent, thorough, and useless.

    The brief youโ€™re handed is rarely the problem youโ€™re being paid to solve. If you want to move from hired expert to trusted advisor, you need to interrogate the request before you fulfil it. Here are three REASONS why answering the brief as given is the most expensive mistake in consulting.

    Reason #1: The Brief Is Written Before the Problem Is Understood

    A brief is not a diagnosis. It is a snapshot of the clientโ€™s current best guess, written by someone inside the problem, usually under time pressure, and often shaped by what they believe they can get approved.

    By the time a brief reaches you, a quiet chain of translation has already occurred. Someone noticed a symptom. Someone else converted that symptom into a presumed cause. A third person converted the presumed cause into a scope of work. Each translation loses information, and each one narrows the field of acceptable answers before an independent mind has examined the evidence.

    This is not a criticism of clients. It is a description of how organisations work. Research bears it out: in a survey of 106 C-suite executives across 91 companies, 85 percent agreed their organisations were bad at diagnosing problems, and 87 percent agreed this flaw carried significant costs.1 These are the people signing your engagement letter. They are telling you, in plain terms, that the problem statement you receive has a high probability of being wrong.

    The advisory move

    Treat the brief as a hypothesis, not an instruction. Before you commit an hour of billable effort, ask the question that reframes everything: โ€œIf we solve exactly what this brief describes, what changes for you?โ€ If the answer is vague, the brief is describing a symptom. Keep asking until you reach a decision someone needs to make. That decision is the real engagement.

    Reason #2: The Client Is Paying for Judgment, Not Compliance

    There is a version of consulting that looks safe: do precisely what was asked, document everything, and deliver on time. No difficult conversations. No challenge to the clientโ€™s framing. It feels professional. It is actually a quiet abdication.

    Clients can buy compliance anywhere. Labour that follows instructions is a commodity, and it is priced like one. What clients cannot easily buy is judgment: the willingness of an experienced outsider to say, โ€œYouโ€™ve asked for X, but the evidence points at Y, and Iโ€™d be taking your money under false pretences if I didnโ€™t tell you.โ€

    This is the foundation of the trusted advisor relationship. Maister, Green, and Galford, in the standard work on the subject, argue that trust is built on credibility, reliability, and intimacy, and destroyed by self-orientation.2 Silently delivering a brief you privately doubt is self-orientation in its most respectable disguise. You are protecting your comfort, your scope, and your invoice, at the expense of the clientโ€™s outcome.

    Here is the paradox worth sitting with: the conversation that feels like it risks the relationship is usually the one that builds it. When you push back on a brief with evidence and care, you demonstrate the one quality that separates an advisor from a contractor. You show the client that your advice is worth more than your obedience.

    The advisory move

    Never contradict the brief with opinion alone. Bring the clientโ€™s own evidence back to them: โ€œHereโ€™s what the data showed when I tested the assumption behind the brief.โ€ Managing client expectations is not about softening bad news. It is about relocating the conversation from what was ordered to what is true.

    Reason #3: The Wrong Problem Compounds With Every Deliverable

    A wrong answer to the right problem gets corrected quickly. A right answer to the wrong problem gets built upon.

    That is what makes this mistake so expensive. Every deliverable you produce against a flawed brief becomes load-bearing. The interim report anchors the steering committee. The options analysis feeds the budget submission. The budget submission shapes the board paper. By the time the mismatch surfaces, unwinding it means unwinding every decision that was stacked on top of it, and your name is attached to the foundations.

    The economics of rework make the point bluntly. Studies of construction projects have measured direct rework costs at around 5 percent of contract value, with indirect costs pushing the true figure far higher.3 Consulting is not different in kind, only in visibility. The rework tax on advisory work is hidden in extended timelines, re-run analyses, and the slow erosion of a clientโ€™s confidence, which is the one asset you cannot re-bill.

    Quality professionals call the underlying pattern the 1-10-100 rule. A problem that costs one unit to prevent at the framing stage costs ten to correct mid-delivery and a hundred to remediate after the work has shipped. Problem framing is the cheapest work you will ever do on an engagement. It is also the work most consultants skip, because it feels like delay and the client is anxious to see activity.

    The advisory move

    Build a framing checkpoint into every engagement, before substantive work begins. One page: the decision to be made, the evidence that would change it, the stakeholders who must accept it, and what โ€œdoneโ€ looks like. If the client wonโ€™t invest an hour in that page, you have learned something important about the engagement you are about to sign.

    The Short Version

    The brief is a hypothesis written by someone inside the problem, so test it before you build on it. The client is paying for your judgment, and delivering silent compliance is a breach of that contract, however polished the deliverable. And a wrong problem compounds: every report stacked on a flawed framing multiplies the cost of the eventual correction.

    None of this requires genius. It requires the discipline to pause at the exact moment when momentum, anxiety, and the clientโ€™s own urgency are all pushing you to start.

    Imagine your next engagement beginning differently. Before a single analysis is run, you and the client agree on the decision at stake, the question that matters, and what a useful answer looks like. Weeks later, your report lands and nobody says, โ€œThis isnโ€™t what we needed.โ€ They say, โ€œThis is what we should have asked for.โ€ That sentence, repeated across a career, is what turns an expert into an advisor, and an advisor into the first phone call.

    When a client hands you their next brief, will you price the work as written, or will you first find out what they are actually trying to decide?


    1 Thomas Wedell-Wedellsborg, “Are You Solving the Right Problems?,”ย Harvard Business Reviewย 95, no. 1 (Januaryโ€“February 2017): 76โ€“83.

    2 David H. Maister, Charles H. Green, and Robert M. Galford,ย The Trusted Advisorย (New York: Free Press, 2000).

    3 Peter E. D. Love, “Influence of Project Type and Procurement Method on Rework Costs in Building Construction Projects,”ย Journal of Construction Engineering and Managementย 128, no. 1 (2002): 18โ€“29.

  • The Practice Leak Most Technical Consultants Donโ€™t See

    The Practice Leak Most Technical Consultants Donโ€™t See

    Most technical consultants are not short of expertise.

    They are short of protected conditions for using that expertise well.

    The options paper gets written between meetings. The expert review happens after three client calls and a morning of email. The proposal follow-up gets pushed to Friday afternoon, then disappears. The client day technically ends, but the unresolved questions, relationship concerns and half-finished deliverables keep running in the background.

    On paper, the practice is busy.

    Client work is moving. Meetings are happening. Reports are being drafted. Questions are being answered. The consultant looks responsive, useful and professionally committed.

    But underneath the activity, the practice may be leaking value in three places.

    The first leak is advisory time.

    This is the time required for deep expert work: technical options assessment, risk judgement, feasibility synthesis, strategic recommendations, expert review, workshop design, due diligence, or the kind of advisory thinking that only works because it comes from years of accumulated judgement.

    This is the work clients are really paying for.

    But in many technical consulting practices, this work happens in fragments. It is squeezed between meetings, interrupted by messages, or pushed to the wrong part of the day when the best thinking has already been spent on operational noise.

    The consultant still produces the work. The client still gets the deliverable. But the work is being produced in conditions that reduce its quality.

    That is the hidden cost.

    The second leak is business development momentum.

    Most independent consultants understand that business development matters. They know they should be maintaining relationships, following up with past clients, publishing useful thinking, refining their positioning, building referral pathways and keeping the next opportunity warm.

    But business development has a structural disadvantage.

    Client delivery has deadlines. Client delivery has people waiting. Client delivery has immediate consequences. Business development is important, but rarely urgent. So when delivery gets heavy, business development quietly disappears.

    The practice then enters the familiar cycle.

    Delivery is full, so business development is deferred. The engagement ends or slows, so the pipeline looks thin. Business development becomes reactive. The consultant starts chasing conversations, rushing proposals, discounting too easily, or accepting work that is close enough rather than right enough.

    Then a new engagement lands, delivery fills the week again, and business development disappears again.

    That is not a discipline problem. It is a practice architecture problem.

    The third leak is recovery capacity.

    This one is easier to ignore because it looks personal rather than commercial.

    The consultant closes the laptop, but the client work does not close with it. An unresolved conversation keeps replaying. A delayed deliverable creates background anxiety. A client email needs a thoughtful response. A proposal is out, but no follow-up has been scheduled. The brain keeps carrying the practice into the evening.

    The cost is not just lower quality rest. It is lower quality thinking the next day.

    For technical consultants, recovery is not a lifestyle luxury. It protects tomorrowโ€™s expert judgement. A tired, mentally loaded consultant does not produce the same clarity, precision or strategic usefulness as one who has properly closed the client day.

    These three leaks, advisory time, business development momentum and recovery capacity, often get mistaken for separate problems.

    • The fragmented expert work looks like a time management problem.
    • The inconsistent business development looks like a sales problem.
    • The client access pressure looks like a responsiveness problem.
    • The evening rumination looks like a work-life balance problem.

    But they usually have the same root cause: the consulting practice is running without a deliberate operating system.

    A technical consulting practice, left to run on default settings, will usually serve todayโ€™s clients at the expense of tomorrowโ€™s practice. Not because the consultant is careless. Usually the opposite. The consultant is committed, responsive and professionally serious.

    That is exactly why the leak happens.

    The calendar fills with client requests. The inbox stays close because responsiveness feels like professionalism. Business development gets fitted into the gaps. Deep advisory work gets done whenever there is a spare block. Recovery depends on whether the day happens to end cleanly.

    That is not a system. That is drift.

    The fix is not to work harder.

    Most technical consultants are already working hard enough. Some are working too hard on the wrong parts of the practice.

    The fix is to identify where the practice is leaking, then install the right control points.

    • What work actually earns your fee?
    • Where is that work being fragmented?
    • Where is business development being displaced?
    • What client access standard have you trained clients to expect?
    • Does the client day actually end, or does it keep following you into recovery time?

    Is there a weekly control loop that catches the drift before it becomes a pattern?

    These are architecture questions.

    And once you see the leak clearly, the next fix becomes much more obvious.

    The Technical Consultantโ€™s Focus System builds the weekly structure that protects these three things:

    1. Advisory time:ย the expert work clients actually pay for
    2. Business development momentum:ย the work that keeps the future practice alive
    3. Recovery capacity:ย the clean end to the day that protects tomorrowโ€™s thinking

    The mechanism is practice architecture: five practical control points that stop the week being run by urgency, client access, operational noise, and good intentions.

    The Technical Consultantโ€™s Focus System: protect your expert work, keep business development moving, and stop client demands from running your week.

  • Expertise Is Not a Business

    Expertise Is Not a Business

    Most consultants started with a version of the same plan.

    Leave employment, take your expertise with you, and build a practice around what you know. Itโ€™s a reasonable plan. For a while, it often works.

    But expertise, by itself, is not a business. Itโ€™s raw material.

    The consultantโ€™s version of the hidden expert problem

    Employed professionals often become hidden experts, doing valuable work that never reaches beyond their employer, team, or immediate manager.

    Consultants face a version of the same problem. The difference is that for consultants, the consequences arrive faster and hurt more directly.

    You can be technically excellent and still struggle to fill your pipeline. You can do outstanding work and still find that clients donโ€™t refer you.

    You can have 20 years of hard-won judgement and still find it difficult to explain your value to a prospect who doesnโ€™t already know you.

    The issue isnโ€™t competence. It almost never is.

    The issue is that expertise and commercial leverage are not the same thing.

    Expertise is capability. Leverage is what it does for you.

    Leverage means your expertise creates options.

    It attracts clients who arenโ€™t just people you already know. It makes you referable to people whoโ€™ve never met you. It gives you a professional identity thatโ€™s bigger than your last client engagement. It lets you choose the work rather than just accepting what comes through.

    Most consultants Iโ€™ve seen struggle commercially are not short on expertise. Theyโ€™re short on leverage. And the reason is usually one of five traps.

    1. The methodology trap.ย Your expertise is real, but itโ€™s trapped inside your own head. You solve problems through instinct and experience, but youโ€™ve never captured the method. That makes you hard to trust from a distance and impossible to price systematically.
    2. The delivery trap.ย Youโ€™re so busy doing the work that you never extract the thinking behind the work. Your insight stays buried in project deliverables, meeting notes, and emails that nobody outside the project will ever read.
    3. The language trap.ย You describe what you do in the language of your discipline, not the language of your clientโ€™s problem. โ€œI provide strategic advisory services in transport planningโ€ is accurate. It is not compelling.
    4. The visibility trap.ย Your reputation is strong with clients who know you. Beyond them, youโ€™re largely invisible. Youโ€™re not creating content, not building public authority, not maintaining a presence that works when youโ€™re not in the room.
    5. The referral trap.ย People like you and respect you, but they canโ€™t easily explain what you do to someone else. If your value isnโ€™t clear and specific, referrals stay soft or donโ€™t happen at all.

    The shift from expert to value creator

    This is where the work is. Not becoming someone youโ€™re not. Not building a personal brand that makes you cringe. Not turning yourself into a content machine.

    The shift is simpler than that.

    Itโ€™s translating your expertise into the language of the problems you solve.

    โ€œI am a civil engineerโ€ is a credential. โ€œI help infrastructure organisations make better long-term investment decisions under uncertaintyโ€ is a value proposition.

    โ€œI am an independent management consultantโ€ is a job description. โ€œI help leadership teams in complex technical organisations align on strategy before they commit capitalโ€ is a commercial statement.

    โ€œI have 25 years in financial servicesโ€ is experience. โ€œI help mid-sized firms understand whatโ€™s actually driving client attrition before they lose another year to the wrong retention strategyโ€ is something a client can act on.

    The translation is not wordsmithing. Itโ€™s the work of understanding exactly who you help, what theyโ€™re struggling with, and what becomes possible when they work with you.

    A quick self-audit

    Ask yourself these questions honestly:

    1. Can you explain what you do in one sentence that a non-specialist prospect would find immediately useful?
    2. Do you have a documented methodology, or is your approach mostly tacit?
    3. Do people who donโ€™t know you well understand what problems to bring to you?
    4. Is your pipeline built on relationships alone, or are there assets working for you when youโ€™re not in front of someone?
    5. If your three best clients stopped renewing, how quickly could you replace that revenue?

    These arenโ€™t branding questions. Theyโ€™re business resilience questions.

    The uncomfortable truth

    Leaving employment was the first act of independence. But professional independence for a consultant isnโ€™t a destination; itโ€™s a discipline.

    It means continually asking whether your expertise is doing commercial work, or whether youโ€™re still hoping that good work will speak for itself. It often mumbles.

    The consultants who build durable, profitable practices arenโ€™t necessarily the most technically accomplished. Theyโ€™re the ones whoโ€™ve done the harder work of making their expertise visible, specific, and easy to buy.

    Thatโ€™s the shift from expert to practice.

    This week

    Write one sentence that translates your expertise into client value. Use this format: I help [specific people] solve [specific problem] so they can [specific outcome].

    Donโ€™t workshop it to death. Get a first draft on paper. That sentence is where your practice starts to get traction.

  • Package Your Thinking or Keep Leaving Money on the Table

    Package Your Thinking or Keep Leaving Money on the Table

    How proprietary frameworks change the commercial structure of your practice

    What if the expertise youโ€™ve spent years developing is worth significantly more than what youโ€™re currently charging for it, and the gap isnโ€™t about skill?

    Most consultants carry their best thinking inside their heads. The ones who build lasting practices put it somewhere else.


    When Bruce Henderson founded the Boston Consulting Group in 1963, he was a one-person operation competing against established management consultancies with deep client relationships and significant resources. He had no institutional brand, no famous alumni network, and no track record as a firm.

    What he had was a way of thinking about business problems that no one had formalised.

    Henderson spent the first years of BCG developing and packaging that thinking into transferable frameworks. The Experience Curve1, the observation that unit costs fall predictably as cumulative output increases, gave clients a new way to understand competitive dynamics. The Growth-Share Matrix2 gave diversified corporations a structured way to decide which business units to fund, grow, and divest. These were not just consulting tools. They were BCGโ€™s intellectual property, proprietary thinking that clients could not get from anyone else.

    The effect on the firm was structural. BCGโ€™s frameworks became the reason to hire BCG. Not a particular partnerโ€™s relationship, not a competitive rate, but the thinking itself. The frameworks preceded the conversation, established credibility, and justified the fee before any proposal was written.

    By the time Henderson retired in 1985, BCG had more than 1,300 employees and offices across the world. The Financial Times, in his 1992 obituary, noted that few people had had as much impact on international business in the second half of the 20th century. He hadnโ€™t built that by being a good consultant. He had built it by packaging what he knew.

    Every consultant should stop treating their expertise as something that only comes alive inside an engagement, and start packaging it into frameworks that work while they donโ€™t. Here are three compelling reasons why consultants who own their thinking win more work, command higher fees, and build practices that scale.


    Reason #1: A Framework Makes Your Thinking Visible Before the Engagement Begins

    Most consultants become credible through delivery. The client hires them; the work is done well; trust accumulates; and, over time, a reputation forms. This is a legitimate path. It is also a slow one, and it depends entirely on clients giving you the first opportunity.

    A proprietary framework inverts the sequence. When your thinking is structured, named, and visible, through a white paper, a methodology described on your website, a model you reference consistently in your content, prospective clients can evaluate your approach before they meet you. The credibility arrives in advance. The first conversation begins from a different starting point.

    This is not a theoretical advantage. Research from VantaInsightsโ€™ 2026 consulting industry analysis found that firms with proprietary frameworks and sector-specific intellectual property are consistently commanding premium pricing, while generalist delivery at standard rates faces increasing margin compression from boutique specialists.3 The mechanism is straightforward: a named framework signals a developed point of view. A developed point of view signals accumulated expertise. Accumulated expertise commands attention before the conversation about fees has begun.

    For a solo consultant without an institutional brand to rely on, this matters more, not less. The large firms have brand recognition and do the pre-selling work. The independent practitioner needs something else. A framework, even a simple one, gives a prospective client something concrete to evaluate, discuss, and anchor their decision on. It makes your thinking legible in the same way that a published book makes an authorโ€™s thinking legible: before you have met them, you already know how they approach the world.


    Reason #2: Named Thinking Commands Higher Fees Than Unnamed Expertise

    There is an important distinction between having expertise and owning it. A consultant who has spent twenty years solving a particular category of problem has genuine expertise. If that expertise exists only as experience, unstructured, unnamed, expressed differently in every engagement, it is difficult for a client to assess its value. Difficult to assess means difficult to price. Difficulty pricing means the default is to compare with whoever else is available, which makes the rate the primary differentiator.

    A named framework changes that dynamic. When a consultant can say, โ€œmy approach to this problem is the X Framework, here is how it works and why it produces better outcomes than alternatives,โ€ they are no longer selling time and effort. They are selling a system. Systems are inherently more valuable than raw effort because they imply repeatability, predictability, and reduced risk. Clients pay more for confidence in the outcome. A named methodology produces that confidence in a way that unstructured expertise cannot.

    The data support this consistently. Research on independent consultant pricing found that those who package their services and price based on outcomes rather than hours systematically out-earn peers operating on hourly billing models, not because their underlying expertise is superior, but because the packaging communicates value more effectively.4 The expertise is the same. The commercial result is different because the presentation is different.

    This is not about fabricating credibility. It is about making genuine credibility visible. The consultant who has developed real expertise over years of practice often undersells it by leaving it unstructured. Packaging that expertise into a named framework is not marketing spin; it is an act of intellectual honesty. It says: I have thought hard enough about this to give it structure. That, in itself, is a signal worth paying for.


    Reason #3: Packaged IP Is the Only Consulting Asset That Scales Beyond Your Available Hours

    Every consultant who sells time hits the same ceiling. There are a finite number of hours in a working week, a finite number of engagements that can be managed simultaneously, and a finite amount of revenue that a practice built on personal delivery can generate. This ceiling is not a failure of effort or ambition. It is a structural feature of any business model that trades time for money.

    Packaged intellectual property breaks the structure.

    A framework, once developed, can be deployed in a workshop, embedded in a diagnostic tool, licensed to other practitioners, published as a book, or taught as a programme. It can generate value for ten clients simultaneously while you are engaged with one. It can work in your absence. It can reach people who will never hire you directly but who will refer others, buy your books, or join your programs. Hendersonโ€™s Growth-Share Matrix didnโ€™t require Henderson to be in the room. It worked, and went on working, because it had been given a structure that existed independently of him.

    A 2025 Harvard Business Review Analytic Services report found that consulting firms leveraging proprietary frameworks and reusable intellectual property delivered up to 40 percent faster time-to-value for clients, compared with firms relying on custom-built approaches for every engagement.5 The client benefit is real. So is the commercial benefit to the consultant: fewer hours spent re-inventing an approach, more consistent outcomes, and a practice that becomes more efficient, not less, as it grows.

    The constraint most consultants face is not a shortage of knowledge. It is a shortage of leverage. Packaged IP is leverage. It is the mechanism by which what you know can reach further than where you are.


    Putting It Together

    The three reasons are connected by a single underlying logic: packaging your thinking makes it work independently of you.

    A framework makes you credible before the client meets you. It justifies a fee structure that reflects the value of a system rather than the cost of time. And it creates assets that compound, generating reach, reputation, and revenue beyond what delivery alone can produce.

    Henderson built BCG on this principle before the concept of intellectual property in professional services had a name. The principle has not changed. What has changed is its accessibility. A consultant today does not need a research team or a publishing deal to package their thinking. They need clarity about what they know, the discipline to structure it, and the confidence to put it in front of the people most likely to benefit from it.

    Imagine what becomes possible when your best thinking is no longer locked inside your engagements, when it exists as something a prospective client can encounter, evaluate, and return to, independent of whether you are available to explain it. That is not a larger version of a consulting practice built on delivery. It is a fundamentally different kind of practice.

    What is one insight, approach, or pattern from your work that you have never named, and what would it take to give it a structure?


    1 https://www.bcg.com/publications/1968/business-unit-strategy-growth-experience-curve

    2 https://www.bcg.com/about/overview/our-history/growth-share-matrix

    3 VantaInsights, โ€œConsulting Industry Trends: Data and Market Analysis 2026,โ€ May 2026, https://vantainsights.com/insights/consulting-industry-trends.

    4 Melisa Liberman, โ€œConsulting Statistics 2025: Insights for Independent Consultants,โ€ melisaliberman.com, August 26, 2025, https://www.melisaliberman.com/blog/consulting-statistics.

    5 Tredence, โ€œ7 Qualities for a Consulting Partner in 2026: Strategy, Execution, and AI,โ€ tredence.com, citing Harvard Business Review Analytic Services 2025 report on proprietary frameworks and reusable IP, https://www.tredence.com/blog/7-qualities-businesses-should-seek-in-their-consulting-partners-in-2026.

  • The Advice No One Asked For

    The Advice No One Asked For

    Why the insight beyond the brief is the one clients remember

    The advice that wins more work is rarely the advice the client asked for.

    Most consultants wait to be asked. The ones who consistently win more work donโ€™t.


    There is a passage in Hold the Line that I return to often when thinking about what retained client relationships actually require. It describes what clients are buying in a retainer arrangement โ€” not a defined deliverable, but something harder to name:

    โ€œOngoing access, expertise, continuity, and the accumulated context that a trusted advisor develops over time. These are real and often substantial forms of value. They are also largely invisible. The value of having a trusted advisor available when a difficult decision arises is not measurable in outputs.โ€

    That invisibility cuts both ways. The advisor who has accumulated genuine context about a clientโ€™s business โ€” its pressures, its internal politics, its emerging risks โ€” possesses something genuinely valuable. But if they only deploy that knowledge when a specific question is asked, most of it sits dormant. The client receives competent delivery. They do not receive the full benefit of what the advisor actually knows.

    The gap between those two things is where the most important consulting relationships are won or lost.

    Every consultant should develop the habit of sharing proactive insight with clients โ€” even when it falls outside the brief. Here are three compelling reasons why giving advice no one asked for is one of the most reliable ways to deepen client relationships and win more work.


    Reason #1: It Changes How the Client Perceives You โ€” From Vendor to Advisor

    The distinction between a vendor and an advisor is not primarily about what you know. It is about how you behave with what you know.

    A vendor performs the work. They arrive with a scope, they deliver against it, and they invoice when the deliverable is complete. This is not a criticism โ€” excellent vendors are genuinely useful. But the vendor relationship has a structural ceiling. The client defines the work. The consultant executes it. The commercial dynamic is transactional, and transactional relationships are, by nature, replaceable. When the project ends, the relationship pauses. When a similar need arises, the client goes back to market.

    An advisor operates differently. They bring observations the client didnโ€™t request. They share a concern that emerged at the edge of their engagement โ€” something they noticed while doing the agreed work that has implications the client hasnโ€™t yet seen. They donโ€™t wait for the question. They bring the answer before the question has been formed.

    This behavioural difference, seemingly small in any single interaction, accumulates into something structural over time. It changes the category the consultant occupies in the clientโ€™s mind.

    Research from Matt Dixon and Rory Channerโ€™s The Activator Advantage โ€” drawn from a quantitative study of nearly 3,000 professional services partners across consulting, law, accounting, and investment banking โ€” found that the top-performing partners shared one defining behaviour: they proactively brought new ideas, risks, and opportunities to clients without being asked. This group, which the research termed Activators, generated disproportionately more work and more durable client relationships than any other type. Only 15โ€“20% of partners naturally operate this way. Yet the behaviour itself is learnable.1

    The first step toward it is recognising that the advice no one asked for is often the advice that matters most. When a consultant surfaces something the client didnโ€™t know to ask about, they are demonstrating something a well-executed deliverable cannot: that they are paying attention to the clientโ€™s world, not just their brief.


    Reason #2: It Increases Client Retention by Making You Harder to Replace

    The economics of client retention in professional services are well established, and consistently underestimated by consultants focused on new business development.

    Bain and Company research โ€” validated repeatedly across professional services contexts โ€” found that a five percent improvement in client retention increases profits by 25 to 95 percent. The range is wide because it varies by practice type and engagement model, but the direction is unambiguous: keeping a client is significantly more valuable, commercially, than finding a new one. The cost of acquisition, the time required to build working context, the revenue gap during transition โ€” all of these accumulate in ways that make existing client relationships among the most valuable assets a practice holds.2

    Yet most consultants manage retention implicitly rather than deliberately. They deliver good work and hope the relationship continues. What they rarely do is actively invest in making themselves harder to replace.

    Proactive insight is one of the most effective ways to do this โ€” not through manufactured contact or formulaic check-in calls, but through the genuine sharing of relevant observations. When a consultant regularly brings something worth thinking about โ€” a risk forming in the clientโ€™s sector, a pattern they are observing across similar engagements, a question the clientโ€™s team hasnโ€™t yet thought to ask โ€” they are building something the client cannot easily find elsewhere: accumulated context applied actively, rather than held in reserve.

    A replacement consultant starts from zero. They do not know the organisationโ€™s history, its internal language, its prior decisions and the logic behind them, the sensitivities that shape how recommendations land. A consultant who has been consistently present โ€” not just in delivery, but in thinking โ€” has built a working knowledge that is genuinely difficult and costly to replicate. Proactive insight is the mechanism through which that knowledge becomes visible to the client, and therefore valued by them.


    Reason #3: It Creates Revenue Opportunities the Client Didnโ€™t Know They Needed

    The most common route to expanded consulting work is the one least often taken deliberately: the client identifies a new need and asks the consultant to help. This is a reasonable development model. It is also entirely passive. The consultant is waiting for the clientโ€™s awareness to catch up with the problem.

    Proactive insight reverses the dynamic. When a consultant brings an observation โ€” a risk, an inefficiency, an emerging issue at the edge of their current engagement โ€” they are not just being helpful. They are surfacing a need that may not yet have a name. And a need with a name is a potential engagement.

    This is not the same as upselling. The distinction matters. Upselling is the consultant looking for opportunities to expand scope for commercial reasons. Proactive insight is the consultant sharing what they genuinely observe, regardless of whether it leads anywhere commercially. The first is self-oriented and clients read it accurately. The second is client-oriented, and clients read that accurately too.

    The commercial consequence of the second approach, however, is significant. Research from SPI Research found that professional services firms running structured client engagement programmes โ€” with regular proactive touchpoints rather than reactive communication โ€” grew revenue 57 percent faster than those without.3 The mechanism is straightforward: clients who are regularly presented with relevant thinking from their advisor identify new needs more readily, because they have a trusted interpreter helping them make sense of their environment.

    The consultant who only speaks when spoken to leaves that interpretive role unfilled. The client either fills it internally โ€” often less effectively โ€” or finds someone else to fill it. Either way, the original consultant has missed the opportunity not through poor work, but through an absence of presence between engagements.


    Putting It Together

    The three reasons are not independent. Each one compounds the others.

    When a client perceives you as an advisor rather than a vendor, they are more likely to stay. When they stay, you accumulate the context that makes your proactive observations genuinely relevant. When your observations are relevant, they surface needs. When needs surface, they become work.

    The mechanism is not complicated. What makes it uncommon is the willingness to act on it consistently โ€” to send the note, raise the question, share the observation, even when there is no immediate commercial reason to do so. The investment is real. The return is disproportionate.

    Imagine what becomes possible when every client you work with thinks of you not as the consultant they hired for a specific project, but as the person they call when something difficult is forming on the horizon. Not occasionally. Reliably. That is not the result of better proposals or more polished presentations. It is the result of a habit โ€” the habit of sharing what you notice, before you are asked.

    What is one observation you are currently holding back from a client โ€” and what would it cost you, actually, to share it?


    Footnotes

    1. Matt Dixon and Rory Channer,ย The Activator Advantage: What Todayโ€™s Rainmakers Do Differentlyย (2025), summarised in Roger Dooley, โ€œThe Activator Advantage with Matt Dixon,โ€ย Brainfluence, May 20, 2025,ย https://www.rogerdooley.com/activator-advantage-matt-dixon/.
    2. Involve Digital, โ€œClient Retention Strategies for Service Businesses 2026,โ€ April 15, 2026,ย https://www.involvedigital.com/insights/client-retention-strategies-professional-services. Citing Bain & Company research on client retention economics in professional services.
    3. Involve Digital, โ€œClient Retention Strategies for Service Businesses 2026,โ€ April 15, 2026,ย https://www.involvedigital.com/insights/client-retention-strategies-professional-services. Citing SPI Research 2026 data on revenue growth in firms with structured client engagement programmes.
  • What Busy Consultants Get Wrong

    What Busy Consultants Get Wrong

    How clarity attracts clients marketing never could

    What if the reason clients arenโ€™t finding you has nothing to do with your marketing and everything to do with your position?

    Most consultants donโ€™t have a marketing problem. They have a positioning problem.


    In an analysis of 140 consultants who consistently generate inbound work on LinkedIn, a striking pattern emerged. Just 19 of them were high-frequency content creators, posting daily, commenting constantly, working the platform hard. The other 121 were barely posting by conventional standards.

    Yet both groups were winning clients.

    The difference wasnโ€™t effort. The high-frequency group worked. It required exceptional content and a community already formed around their ideas. The 121 others had stopped optimising for engagement and started optimising for something more fundamental: being found by the right people in the right way.

    What separated them wasnโ€™t volume. It was positioning. They knew, with uncommon specificity, what problem they solved, for whom, and why it mattered. Their occasional posts didnโ€™t need to go viral because when the right person encountered them, the message was unambiguous.

    The analyst who ran the research put it plainly: most LinkedIn activity is productive procrastination. Activity keeps you busy. Positioning keeps you booked.1

    The distinction matters more than most consultants realise, and it is the one most consistently ignored in favour of tactics.

    Every consultant can build a position that attracts qualified work, without posting daily or chasing the algorithm, by taking three deliberate steps to define what they stand for and who they stand for it with.

    Step #1: Achieve Clarity on the Problem Only You Are Positioned to Solve

    Positioning begins with a question most consultants find genuinely uncomfortable: what is the specific problem you solve, stated precisely enough that the person experiencing it would immediately recognise themselves in the description?

    Not โ€œI help organisations improve performance.โ€ Not โ€œI support leaders through change.โ€ These are categories, not positions. They describe what you do in the same terms that fifty other practitioners would use. A prospective client scanning them has no way to distinguish you from anyone else, which means the primary differentiator becomes price.

    The problem with imprecise positioning is not that it attracts too few clients. It is that it attracts the wrong ones, clients who arrived not because they believed you were uniquely suited to their situation, but because you were available and your rate was acceptable. Those engagements are harder to price, harder to scope, and harder to do well.

    Clarity about your core problem changes the structure of the commercial conversation before it begins. When a prospective client arrives, having encountered your thinking on the exact challenge they are facing, the first conversation does not need to establish credibility. It begins from it. The positioning has already done the persuasion work in advance.

    This is the mechanism behind a finding that should give every generalist pause: according to data from a study of consultants across practice areas, 52% of niche specialists charge $10,000 or more per project, compared with just 18% of generalists achieving the same rate.2 The revenue gap is not primarily a function of skill. It is a function of perceived fit, and perceived fit is a positioning outcome.

    The diagnostic question is straightforward. Can you describe the problem you solve in a single sentence that is specific enough to be wrong for most people, but unmistakably right for the client you are best equipped to serve? If the answer is no, you do not yet have a position. You have a service description.

    Step #2: Achieve Specificity About the Client Most Likely to Have That Problem

    A defined problem still requires a defined client. The two are not the same, and conflating them is one of the more common errors consultants make when trying to sharpen their positioning.

    You can name a problem with precision and still leave the client undefined. โ€œHelping engineering firms reduce project overrunsโ€ is more specific than โ€œhelping organisations improve performance,โ€ but it still leaves open a wide range of client types, small firms, large firms, public sector, private sector, different technical disciplines, each of which has a different context, a different decision-making process, and a different set of concerns about engaging outside help. Content that speaks to all of them simultaneously speaks compellingly to none of them.

    Specificity about the client is what makes the positioning legible to the people who refer work. Referral networks operate on pattern recognition. When someone in your network encounters a prospective client with a problem, the name that surfaces is the name most clearly associated with that type of problem for that type of client. Generalist positioning produces vague referrals. Specialist positioning produces actionable ones.

    Research on specialist versus generalist framing consistently finds that specialist positioning triggers higher trust, particularly when a prospective buyer is making fast judgements, which is the normal condition for senior professionals evaluating whether to engage outside expertise.3 The client is not conducting a rigorous procurement process. They are quickly asking themselves whether this person understands my situation. Specificity answers that question before they have to ask it.

    The practical test is this: can you describe your ideal client specifically enough that they would recognise themselves, and broadly enough that there are sufficient numbers of them to sustain a practice? A client defined by industry, seniority, and the specific trigger that typically prompts them to seek outside help is usually specific enough to be memorable and broad enough to be commercially viable.

    Step #3: Achieve Consistency Across Every Channel Before Scaling Any Marketing Activity

    The third step is the one most commonly skipped, which is why the first two steps so rarely produce the results they should.

    A consultant who has achieved clarity on their problem and specificity about their client still needs to ensure that the position is communicated consistently across their LinkedIn profile, website, email signature, how they introduce themselves at a conference, and the language in their proposals. Inconsistency between these touchpoints forces the prospective client to resolve the contradiction themselves, and most will not bother. They will simply move on.

    This is where the 121 consultants in the earlier study had an advantage; the high-frequency posters often lacked. Their positioning was coherent. Every place a prospective client could find them told the same story. Their low posting frequency was not a liability because the message’s consistency compensated for the volume.

    Consistency also produces a compounding effect that is difficult to manufacture through marketing activity alone. Research on niche-focused practices consistently finds that the compounding benefits, stronger referrals, better qualified enquiries, and reduced price sensitivity typically begin to gain traction after six to twelve months of consistent positioning.4 This is not a particularly long horizon by any standard business measure. But it does mean that consistency must precede scaling. Scaling an inconsistent position accelerates noise, not signal.

    The practical sequence is to audit every client-facing touchpoint against a single positioning statement before producing any new content. If the profile, the website, the introductory language, and the proposal template all reflect the same position, you are ready to increase marketing activity. If they do not, more content will compound the confusion.

    Putting It Together

    The three steps are not independent. Each one builds the conditions for the next.

    Clarity on the problem gives you something worth saying. Specificity about the client gives you someone worth saying it to. Consistency across channels ensures that the message reaches the right person in a coherent form, regardless of where they first encounter your work.

    Marketing activity, content, posts, outreach, and speaking are most effective when they build on a clear position. Without that foundation, activity produces impressions. With it, the same activity produces enquiries from people who, before they contact you, have already concluded that you are likely the right choice.

    The consultants who generate the most consistent inbound work are rarely the most visible. They are the most clearly positioned. Visibility follows positioning. It does not substitute for it.

    Imagine what becomes possible when every prospective client who encounters your work, whether through a post, a referral, or a profile search, arrives already understanding what you do, who you do it for, and why that matters to them. Not occasionally. Reliably. That is not the result of a better content strategy. It is the result of a clear position, consistently held.

    What would a prospective client find if they searched for you today; and would it be specific enough to make them feel they had found exactly the right person?


    Footnotes:

    1 Melanie Goodman, โ€œI Analysed 140 LinkedIn Profiles,โ€ย Substack, April 2026, https://melaniegoodmanlinkedinconsultant.substack.com/p/i-analysed-140-linkedin-profiles.

    2 Simply.coach, โ€œ23 Consulting Niches That Actually Make Money (And How to Choose Yours),โ€ Simply.coach Blog, 16 January 2026. https://simply.coach/blog/profitable-consulting-niches/

    3 Yoon Jae Koh and S. Shyam Sundar, โ€œHeuristic versus Systematic Processing of Specialist versus Generalist Sources in Online Media,โ€ย Human Communication Researchย 36, no. 2 (2010): 103โ€“124

    4 ContempThemes, โ€œThe Economics of Niche Positioning in Real Estate,โ€ ContempThemes.com, 5 March 2026

  • How Clients Decide Whether to Trust You

    How Clients Decide Whether to Trust You

    Three things clients observe before they decide to give you real access

    Your new client is already deciding whether to trust you. The question is whether you know which moments theyโ€™re using to make that call.

    In The Trusted Advisor, David Maister and his co-authors open with an observation that most consultants find uncomfortable: clients almost never evaluate you on the quality of your technical work, at least not initially. They canโ€™t. They donโ€™t have the expertise to assess whether your methodology is superior or your analysis is the best available. What they can assess, and what they assess continuously in the early weeks of an engagement, is whether you seem to be on their side.

    Maister describes a pattern repeated across law firms, consulting practices, and accounting firms. Advisers who led with credentials, frameworks, and prior case studies tended to win engagements on paper and lose the relationship in practice. Clients felt processed rather than heard. The advisers who slowed down, asked questions they didnโ€™t already know the answer to, and demonstrated genuine curiosity about the clientโ€™s specific situation were the ones who received referrals, repeat work, and access to senior stakeholders that the technically superior advisers never reached.

    The trust was not built through competence. It was built through behaviour. Small, early, observable behaviour.

    The client across the table from you is running a quiet assessment you were never told about. Here are three behaviours that determine whether you pass it or fail it, often without realising either has happened.

    Behaviour #1: Whether You Slow Down to Understand Before You Move to Solve

    The instinct is understandable. You were hired for your expertise. The client has a problem. The problem looks familiar. You know what good looks like. The temptation is to move quickly toward the answer, because speed signals competence, and competence is what you are being paid for.

    This instinct, reliably, costs you.

    What the client observes in those early interactions is not whether you have the right answer. They cannot yet verify that. What they observe is how you treat their version of the problem before you have imposed your own. If you move quickly to solve, the implicit message is that you already understand enough that their context, their constraints, and their specific history with this issue are not particularly relevant to the solution you have in mind.

    That message lands. Clients rarely articulate it. They simply become less forthcoming. The information they share becomes more curated. The access they grant becomes more managed. The relationship settles into something cordially professional that never becomes genuinely useful.

    Edgar Schein spent five decades studying helping relationships across organisations and distilled his observations into what he called humble inquiry, the practice of asking questions driven by genuine curiosity rather than questions designed to confirm what you already believe you understand.1 The distinction, he found, was visible to the person being asked. Clients know when they are being listened to and when they are being processed. They adjust their behaviour accordingly.

    Slowing down is not a soft skill. It is a trust mechanism. The consultant who takes longer to understand earns earlier access to the real problem. The one who moves quickly to solve often spends months working on a version presented.

    Behaviour #2: Whether Your Attention Is on the Clientโ€™s Problem or Your Own Performance

    Every consultant enters an engagement with something at stake beyond the work itself. There is a reputation to maintain. There is a first impression to manage. There is an anxiety, often unspoken, about whether this client will come away satisfied, and what they will say to others if they are not.

    That anxiety is normal. What matters is where it directs your attention.

    A consultant whose attention is oriented toward their own performance, toward how they are coming across, whether they are being perceived as capable, whether the client seems impressed, is in a fundamentally different relational posture than one whose attention is on the clientโ€™s actual situation. The difference is detectable, even if the client cannot name it precisely.

    Research in organisational psychology on what is termed self-focused versus other-focused attention in advisory contexts consistently finds that clients report higher trust, greater candour, and stronger satisfaction in relationships where they perceive the adviser to be primarily engaged with their problem rather than their own image.2 This is not about suppressing professional confidence. It is about the direction of attention in any given conversation.

    The practical signal is simpler than it sounds. A consultant oriented toward their own performance tends to talk more in early meetings, filling the silence, volunteering analysis, and demonstrating that they have thought about the problem. A consultant oriented toward the clientโ€™s situation tends to ask more, listen without immediately moving to interpretation, and tolerate not having an answer until one is genuinely warranted.

    Clients notice which mode you are in. They do not describe it in those terms. They describe it as: he really seemed to get it. Or: Iโ€™m not sure she was really listening. Those assessments are made early, they are sticky, and they shape the quality of information you receive for the remainder of the engagement.

    Behaviour #3: Whether You Keep Small Commitments No One Is Tracking

    Trust in a professional relationship is not established through a single significant gesture. It is established through the accumulation of small, kept commitments, most of which the client registers without ever explicitly noting.

    You said you would send the document by Thursday. It arrives on Wednesday afternoon. You mentioned you would look into a specific issue and come back with a view. You come back with the view, unprompted, at the next meeting. You committed to keeping a particular piece of information within the immediate team. It stays there.

    None of these actions is remarkable in isolation. Collectively, they answer a question the client is continuously running in the background: Is this person reliable when no one is watching?

    This matters more in consulting than in many other professional contexts because consulting engagements routinely involve information asymmetry. The client knows things about their organisation that you do not yet know. Whether they share those things, the real budget, the internal politics, the prior failures, depends entirely on whether they believe you will handle the information with care and follow through on what you say. That belief is not formed by your credentials. It is formed by the pattern of small behaviours in the first weeks of the engagement.

    Charles Green, one of Maisterโ€™s co-authors on The Trusted Advisor, later developed what he called the Trust Equation, a framework for understanding what drives client trust in professional relationships. The equation identifies four components: credibility, reliability, intimacy, and self-orientation. Of these, reliability, doing what you say you will do consistently, in small things, is the component that advisers most frequently underestimate and clients most consistently weigh heavily in their assessments.3

    The logic is straightforward. Credibility is claimed. Reliability is demonstrated. Clients have limited means to verify the former. They have continuous visibility into the latter.


    Putting It Together

    The three behaviours are connected by a single underlying dynamic: trust is formed through observation, not declaration.

    You cannot tell a client you are trustworthy. You cannot establish it through a credentials deck or a well-constructed proposal. You establish it through the small, unremarkable moments that occur continuously in the early weeks of an engagement, how you listen, where your attention sits, and whether you follow through on the things no one is tracking.

    The difficulty is that these moments do not feel significant when they occur. That is precisely why they are effective signals. A client who sees a consultant slow down to understand rather than rushing to solve, maintain attention on the problem rather than their own performance, and keep commitments without being reminded is observing a pattern of behaviour that tells them something reliable about what the next twelve months will look like.

    That pattern, once established, is the foundation for everything else, the candour, the access, the quality of information that makes the difference between good consulting and exceptional consulting.

    The trust threshold is real. Most clients never announce it. The ones who do are typically the ones you never quite reach.

    Where in your current engagements are you moving to solve before you have fully understood? And what might that be costing you?


    Footnotes

    1 Schein, Edgar H.ย Humble Inquiry: The Gentle Art of Asking Instead of Telling.ย Berrett-Koehler Publishers, 2013. Chapter 2, โ€œThe Primacy of Humble Inquiry.โ€

    2 See the broader literature on adviser attention orientation in professional service contexts, including work building on Maister, Green, and Galfordโ€™s foundational research.

    3 Green, Charles H., and Andrea P. Howe.ย The Trusted Advisor Fieldbook.ย Wiley, 2012. Chapter 3, โ€œThe Trust Equation in Practice.โ€