USE /working-with

How to collaborate effectively

How to engage

• Agree the destination first: Outcomes, constraints, and success measures before method talks.
• Hand over a domain: Clear authority, then short progress reviews instead of constant check-ins.
• Surface risk while it is cheap: Facts and options early, not post-mortems after the window closes.
• Leave the path open: Once the goal is clear, trust independent judgement on how to get there.

Communication that works

• Lead with the point: Then the evidence. Long warm-ups waste energy on both sides.
• Tie feedback to outcomes: Decisions land better when they reference results, not vibes.
• Meetings need a job: Agenda, active tasks, and a decision or next step.
• Account for written load: Dyslexia makes long, high-volume written threads harder than verbal clarification.

Where I add most value

• Complex product and platform delivery where architecture, delivery, and ops have to stay aligned.
• Technical direction that stays hands-on: setting patterns, unblocking teams, and shipping.
• Platform, DevOps, and quality practices that make the next release safer, not just the current one.
• Mentoring and standards so the team still holds together after handover.

Best fit / friction

Best fit

• Clear ownership and measurable targets.
• Autonomy on method after goals are agreed.
• Direct, fact-based collaboration with product and delivery.
• Work where urgency and risk identification matter.

Friction

• Vague goals with no agreed definition of done.
• Meeting-heavy process that avoids decisions.
• Low-autonomy execution with little ownership of the domain.
• Written-only cultures that leave no room to clarify in conversation.