Lead clearly across languages, cultures and high-stakes decisions.

“When I became responsible for Asia-Pacific, I inherited a Japan-based capacity and supplier-resilience programme that required support for a phased $18 million investment. The technical case was strong, but the decision had stalled after 2 reviews.

Our Japan team believed headquarters was underestimating operational dependencies. Headquarters saw the Japan papers as detailed but noncommittal. I had led businesses across several markets and did not need another presentation course. I needed to turn competing technical, financial and cultural perspectives into one decision the board could understand, test and act on. At the next review, the programme received first-cycle conditional approval; our finance team estimated that this brought implementation forward by 11 weeks and avoided approximately $620,000 in duplicated engineering, contractor-holding and review-related costs. The work behind that result began when...

READ FULL TESTIMONIAL HIDE TESTIMONIAL

Mark worked with the actual material and the people I had to move: the board paper, engineering assumptions, finance sensitivities, partner commitments and the questions already raised by global operations. Before editing the language, he challenged the decision architecture. What precisely required approval? Which risks were material? What evidence would change our recommendation? Which conditions could we accept without weakening the programme?

We rebuilt a 22-page paper as a 6-page decision brief with 1 clear recommendation, 2 contingencies and 3 stage gates. The technical detail remained available, but the main narrative connected capacity, customer exposure, implementation risk and capital discipline. We then rehearsed 28 likely questions, including the questions I least wanted to receive.

The work also covered how I led the conversation: disagreeing with a board member without becoming defensive, interrupting a technical detour, translating a Japan-specific constraint without presenting it as an exception, and making the decision request again after the discussion changed direction. Mark understood that the same words can signal confidence, resistance or ambiguity differently across Japan, regional leadership and global headquarters.

Across 4 months, we worked through 12 live cases and 7 recorded rehearsals. My time to recommendation in prepared reviews fell from approximately 9 minutes to under 3, and each of the following 5 steering meetings ended with a decision, named owner and next date.

At the next board review, the programme received conditional approval in the first cycle. Compared with the resubmission timetable, our finance team estimated that this brought implementation forward by 11 weeks and avoided approximately $620,000 in duplicated engineering, contractor-holding and review-related costs. The economics and the technical work made the investment viable; clearer executive communication made the trade-offs and controls sufficiently visible for a decision to be made.

The greatest value was having an external thinking partner who could work across strategy, leadership behaviour and communication without oversimplifying the business. The engagement did not merely improve a presentation. It improved how I converted complex regional evidence into decisions with financial and operational consequences.”

CLOSE TESTIMONIAL ↑

“As we moved from custom AI pilots toward a scalable enterprise platform, I was leading product, engineering and research teams across North America, Japan and Europe. The market was moving faster than our existing management rhythm.

Our 8-person leadership team was intelligent and committed, but meetings mixed exploration, advocacy and decision-making. A strong opinion from a senior leader could be interpreted as a final decision, important objections surfaced after the meeting, and teams sometimes continued investing because no one had explicitly called for a reset. We did not need more leadership vocabulary. We needed a better way to think, challenge and decide together. Under the new operating rhythm, one product reset was made 7 weeks earlier; finance estimated that the decision avoided approximately $1.1 million in additional engineering and cloud expenditure and released 14 specialists to 2 higher-priority products. The change began when...

READ FULL TESTIMONIAL HIDE TESTIMONIAL

Mark worked with the live issues already on our agenda: product-scope decisions, model evaluation and risk, an enterprise launch, a senior leader whose function was missing commitments, and a Japan-based strategic customer whose expectations were being interpreted differently by product and commercial teams.

We reviewed meeting transcripts, decision papers and the language each leader used when proposing, questioning, disagreeing and closing. This revealed that our problem was not simply meeting discipline. We had unclear decision rights, inconsistent standards of evidence and no shared way to distinguish a reversible experiment from a commitment with material customer or cost consequences.

Together we redesigned the weekly leadership meeting around decision type, owner, criteria and dissent. Mark helped me state when I was offering a hypothesis, requesting challenge or making a decision. We also established how a leader could disagree with urgency without being labelled resistant, and how the team would communicate a final decision consistently across different regions and functions.

The cross-cultural work was particularly important. Direct challenge that felt efficient in one office could close down contribution in another; extensive context that showed diligence to one team could sound evasive to another. We developed language that preserved the substance of disagreement while making intent, authority and the next action unmistakable.

Comparing the 8 weeks before and after the new operating rhythm, the leadership meeting moved from an average of 105 minutes to 68. Decisions reopened after the meeting fell from 12 to 3, and agenda items ending without a clear owner or criterion fell from 18 to 5. In an anonymous pulse survey, the proportion of leaders who agreed that they could challenge an important decision before commitment increased from 58% to 84%.

One product reset was made 7 weeks earlier than under our previous review process. Finance and the programme office estimated that the earlier decision avoided approximately $1.1 million in additional engineering and cloud expenditure, released 14 specialists to 2 higher-priority products and brought a strategic enterprise pilot forward by 6 weeks. Communication did not create those economics by itself; it allowed the evidence, disagreement and decision to happen before further cost accumulated.

This was not motivational coaching and it was not communication as polish. It strengthened the management system through which we allocated attention, challenged assumptions and committed resources. I became more deliberate about where my authority was necessary and where the organization needed a clearer question rather than another answer from me.”

CLOSE TESTIMONIAL ↑