Notes from inside the work.

Takeaway

The tracker, scorecard, or plan is rarely the important artifact. Any decent methodology calls these out, I've worked in most of them. The value is in making dependencies visible, tying decisions back to their purpose, and showing where yesterday's alignment needs revisiting. As an outside advisor, I get to ask the questions busy teams often don't have the space to ask: does this still line up with that other decision, or are we drifting? What about the person still delivering against the old decision, do they know it changed? What tradeoff actually brought us here? Do we address the consequence now, or plan for it later?

Takeaway

Early in my career, I learned the mechanics of consulting by doing them. I reran the numbers, fixed the fonts, aligned the text boxes, revised the proposal, and listened as senior partners debated a single word. AI can now do a meaningful share of those mechanics. That is real progress, and organizations should pursue it. Most of my daily AI use is deliberately ordinary. It helps draft standard invoice language, organize internal notes that contain no confidential client information, structure CRM tasks within approved systems, prepare outreach, refine public writing, build checklists, and test different ways to express an idea. It handles first passes and administrative friction. I review the work, make the decisions, and own the final output. What AI cannot reproduce is the experience happening around the task: why a word mattered, which executive should open the meeting, who should answer the difficult question, what we knew about the client's stakeholders, history, and values that changed how the recommendation should be presented. An AI model can process the record of experience. It cannot have the experience, read the room, or accept responsibility for the decision.

Takeaway

Haste rarely presents itself as compromise. It feels like momentum. Take the meeting. Use the provider's framework. Start the demonstration. Borrow the evaluation criteria. A provider recently offered to write a client's capital request. Helpful on the surface, but it would have let the proposed solution begin writing its own business case. Each shortcut feels reasonable. Together, they can leave a team comparing solutions before agreeing on what it is trying to protect. Values, in this context, are not words on a wall. They are the choices a team wants its decision to honor when attractive options pull in different directions. Speed or control? Consistency or local flexibility? Immediate relief or a capability that will last? Provider perspectives are useful. Peer experience is useful. Understanding why a company invests in certain parts of its roadmap is useful. The problem begins when those inputs stop informing your values and start replacing them. A good competitive process makes the team's values explicit, reconciles the differences among stakeholders, and turns what matters into criteria providers can respond to. The result is more than a defensible selection. It is a decision that still feels right after the sales cycle ends.

Takeaway

A line commonly attributed to Mark Twain says, "I would have written a shorter letter, but I did not have the time." It appears the thought actually belongs to Blaise Pascal, which I appreciate even more. I learned the basics of programming in the language named after him. Long before I understood how much structure matters in communication, Pascal was teaching me structure in another form. That part of the lesson simply took longer to compile. The point is that brevity takes time. Most of us share too much because we are afraid of leaving something out. That transfers the work to the reader, who now has to search through our thinking to find the point. Brevity and completeness are not opposites. Good formatting lets you provide both. Put the takeaway first, organize the evidence beneath it, and let the reader decide how deeply to go.

Takeaway

Your list of AI pilots is not your differentiation. Your industry peers are holding nearly the same list. Differentiation begins with what happens next. Which pilots do you scale? Which do you stop? Where should capabilities be consolidated? Which provider dependencies have become material? Do the contracts and governance reflect the maturity and consequences of the deployment? That is the discipline organizations tend to fund too late: a portfolio view, honest stop and scale decisions, contract and dependency terms someone has actually stress tested, and governance that matches what the technology has become.

Takeaway

Expertise does not exempt you from your own advice. It simply makes it easier to convince yourself that you are the exception. I am not. Nobody is. The discipline I bring to a client's business has to exist in my own. That means creating enough structure to know where my time is going, which opportunities deserve more attention, and when being helpful has started to become unpaid delivery. Without that structure, ambition can look a lot like progress while producing very little of it.

Takeaway

The activation gap is usually not a skills problem or a people problem. It is a structural problem. Someone needs to sit between the executive who said "go" and the team that heard "go... where?" That someone builds the execution architecture, aligns the stakeholders, and creates enough clarity that the team can sustain momentum without them. Then that someone leaves.

Takeaway

I am rarely a line item in the original budget. The need for my work becomes visible when a leader replaces the progress story with a clear view of what is actually stuck. When I hear, "Everyone is busy, but nothing is moving," I ask each person what they believe the priority is. Four or five conversations usually produce four or five different answers. This takes less than half a day to compile. That mismatch is not a failure of the team. It is evidence that the decisions, tradeoffs, and ownership have not been made clear enough for the work to move. The budget does not appear because outside help suddenly became inexpensive. It appears because the cost of waiting became impossible to ignore.

Takeaway

Trust is the most undervalued asset in professional services. Most firms optimize for utilization. The ones that optimize for trust build something that compounds. I try to operate this way every single time: stay until the work sustains itself, then leave. If the work is good, the phone rings again.

Takeaway

This was not bad strategy. It was strategy that stopped before ownership, sequencing, and decisions had been made executable. That distinction matters. The engagement had been designed to deliver a strategy. The client believed it had also purchased movement. In three weeks, I translated more than 200 pages into a four page execution roadmap with named owners, weekly milestones, and clear escalation triggers. The team started moving in the first week. A strategy does not become valuable when it is approved. It becomes valuable when people know what they own next.

Takeaway

Contracts get treated as legal's job, read once at signing and then filed away. I treat them as a live strategic asset. Every renewal, every vendor tension, every "can we get out of this" conversation starts with me reading the actual document again, not the institutional memory of what it says. Institutional memory needs reminders.

Takeaway

Nobody needed a new technology. They needed someone to thread together hundreds of data points across lab systems, cold chain logistics, hospital intake, and parent-facing visibility into one coherent patient journey. Offerings developed for the platform support CAR-T programs across four manufacturers and thousands of patients.

Takeaway

I've learned to spot this in the first week of any engagement. It usually comes with two other symptoms: no one can articulate the actual goal in the same way, and the team has stopped asking clarifying questions because they've been punished for it. If I see all three, the first conversation is with the leader, not the team. The team isn't the problem.

Takeaway

Most consultants start with the work. I start with the people. Because the work is never what's stuck. What's stuck is the misalignment between the people who need to agree on what the work even is.

Takeaway

In 25+ years, I can count the number of times this has happened on one hand. The teams that treat external partners as full members of the crew consistently outperform. Not because the contractors work harder out of gratitude (though that happens), but because information flows freely when there's no caste system. The best intelligence about what's really going on often lives with the people who are closest to the work but furthest from the org chart.

Takeaway

Ambition and hard work do not circumvent reality. I vowed never to overstate capabilities again, and that conviction shaped every deal I scoped and priced from that point forward. If I tell you I can do something, it's because I've done it or something genuinely close to it. If I haven't, I'll say so.

Takeaway

My whole model is "work yourself out of a job." When I violate it, the client suffers, even if they don't realize it yet. Dependency is comfortable but corrosive. Now I have a hard rule: at the end of every month, I ask myself whether the team would be meaningfully worse off without me. If the answer is no, it's time to have the conversation.