A living operating manual.

A strange amount of my life has begun by pressing yes before reading the whole dialogue box. That is useful when the decision is reversible and reality can teach faster than research. It is reckless when other people, clinical claims, money or long-term commitments carry the cost.

So I move quickly into low-risk experiments and deliberately slow down at consequential edges.

• Reversible in a week? Try it rather than argue about it.
• Someone else carries the downside? Slow down and name who decides.
• Never let momentum make a claim the evidence cannot support.

Evidence: London Fashion Week · Berkeley Leadership Week · Synetra Health

Ambition is not coordination. Before a project can move, people need a shared sentence for the problem, a visible next artefact, an owner and a reason to care.

Much of my work is translation: turning a chaotic intention into a shape that designers, operators, partners, users and sceptics can all act on.

• One sentence for the problem that a stranger can repeat back.
• One visible next artefact, not a roadmap.
• One named owner per decision.

Evidence: Creative Entrepreneurs Society · Prismatic · Cartoon Museum

An event begins long before the first speaker and continues after the last person leaves. Venue, arrival, social permission, food, pacing, who is introduced to whom and what happens next all alter the outcome.

I treat events as temporary universes: small systems that make particular behaviours more likely for a few hours.

• The venue decides more of the evening than the programme does.
• Design the first five minutes and the last five minutes hardest.
• Someone must be responsible for introductions, or nobody meets anybody.

Evidence: Designing Temporary Universes · CES × Lovable Showcase Gala

Teams often debate the most visible part of a problem while a quieter constraint controls everything. In an event it may be the venue or the dropout rate. In a product it may be power, connectivity, workflow or trust.

I try to identify the variable that makes the rest of the argument cosmetic.

• Ask which assumption, if false, makes the whole plan pointless.
• Test that one first, cheaply.

Evidence: Synetra Health · Cartoon Museum

A compelling story can make a weak idea feel finished. The antidote is contact with the people and conditions the work is meant to serve.

Interviews do not prove that a solution works. They can tell you that your original problem was imaginary, your language is wrong, or your assumptions are expensive.

• Talk to the people inside the problem before writing anything down.
• Report what conversations disproved, not only what they supported.

Evidence: Synetra Health · Philips DPS placement

Collaboration should widen the thinking without dissolving responsibility. I prefer one clearly named owner for each decision, generous context for everyone contributing, and explicit credit when the work ships.

“We all own it” too often means nobody knows who closes the loop.

• Name the owner in writing, at the time.
• Credit by name when it ships — including the parts you did not do.

Evidence: Creative Entrepreneurs Society · European Innovation Academy

Documentation written during a crisis is archaeology. Roles, formats, decisions, contacts and recurring tasks should be captured while the people who understand them are still present.

The test of a community or programme is not whether I can run it again; it is whether someone else can make it better without reconstructing the past.

• Write the handover in month one, not month eleven.
• Three repeatable formats beat thirty bespoke events.
• If attendance depends on one person being in the room, the system is unfinished.

Evidence: Creative Entrepreneurs Society

Busy teams can become very attached to the performance of effort. Meetings multiply, messages accelerate and everyone appears indispensable — while the result remains politely unexamined.

I want the intended change, the evidence and the review date named early enough that the project is allowed to disappoint us.

• Name the change you expect, and how you would notice it.
• Set the review date before the work starts.

Evidence: London Venture Run · Quorum

Finished work compresses away the useful knowledge. I record the discarded idea, the awkward conversation, the last-minute venue problem, the prototype that failed and the decision that changed direction.

Those details make a case study honest and make the next project less dependent on memory.

• Write the log during, not after.
• Publish the failure with the same specificity as the win.

Evidence: Maps, Mechanics, and a Very Bad Sleep Schedule · Data… data… and more data!

Entering a new discipline does not require pretending to be an expert. It requires enough vocabulary to ask non-wasteful questions, enough safety to avoid obvious harm, and enough humility to keep learning from people with deeper practice.

I learn in layers, because the next useful question is often invisible until something has been attempted.

• Learn enough to act safely, then let contact with reality set the syllabus.
• Defer to deeper practitioners in public, not only in private.

Evidence: Parsons intensive · UAL Creative Hack

• Activity is not proof.
• Attendance is not community.
• A logo is not a partnership.
• An interview is not validation.
• A target is not an outcome.
• A framework is not a substitute for judgment.
• Ambition is not permission to overclaim.
• “Multidisciplinary” is not an excuse for incoherence.
• Personal vulnerability is not automatically public content.
• If a project needs me in every room, the system is unfinished.