mike/oc-site
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Rewrite 'How we work' as the three-places model (Inga's feedback)

Browse Source 
Replaces the model-teaching cards (and the 'Clear models / not just a
workshop' heading) with Inga's concrete framing: the work happens in three
places — the people who carry the knowledge (coaching), the team that has to
get on board (facilitation), and the process that could work better
(redesign). Stacked editorial rows; new .work-list styles.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Michael Victory
2026-06-22 06:37:52 -07:00
parent 13625a8db0
commit 3adce443d1
2 changed files with 40 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
index.html
+31 -19
View File
@@ -111,29 +111,41 @@
<section class="band light services" data-bg="light" id="work">
<div class="wrap">
<p class="eyebrow">How we work</p>
<h2>Clear models, <em>not vague advice.</em></h2>
<p class="section-intro">The kind you can use in a hallway conversation, not just a workshop.</p>
<div class="cards">
<article class="card">
<p class="card-tag">A shared lens</p>
<h3>A shared language</h3>
<p>When a conversation gets tense, people are either open and curious or closed and out to be right — and most teams have no shared way to name which is happening. We give them one. Once a team can name it, the hard conversations get easier instead of louder.</p>
<p class="outcome">A shared, plain-spoken way to handle friction.</p>
<h2>The work happens in <em>three places.</em></h2>
<p class="section-intro">Depending on what's actually getting in the way.</p>
<div class="work-list">
<article class="work-item">
<div class="work-head">
<h3>The people who carry the knowledge</h3>
<p class="work-deliver">Delivered through one-to-one coaching, scheduled around their calendar.</p>
</div>
<div class="work-body">
<p>Every shop has someone whose expertise is real and hard-won and almost entirely in their head. When they leave, retire, or just get pulled in another direction, that knowledge leaves with them.</p>
<p>We work directly with those people — not to extract what they know and hand it to a system, but to help them see the value in passing it on and actually want to do it. That usually takes more than one conversation. It takes someone who can ask the right questions, earn the trust, and help them work out what letting go actually means for them.</p>
</div>
</article>
<article class="card feature">
<p class="card-tag">The core shift</p>
<h3>Breaking the blame game</h3>
<p>Under pressure, shops fall into blame: someone stuck feeling powerless, someone doing the blaming, someone forever swooping in to rescue — and burning out. It quietly kills change. We move people out of that cycle and into owning the outcome together.</p>
<p class="outcome">Stop the blame cycles that stall every change.</p>
<article class="work-item">
<div class="work-head">
<h3>The team that has to get on board</h3>
<p class="work-deliver">Delivered through facilitated sessions — one-off or a short series — with the team or a cross-section of it.</p>
</div>
<div class="work-body">
<p>A change announced is not a change adopted. The people affected by it usually have something to say — about what's getting lost, about whether it'll actually work, about what they're worried won't be considered. When that stays unsaid, it surfaces later as resistance, workarounds, or quiet non-compliance.</p>
<p>We create the conditions for that conversation to happen before the rollout, not after. When people have real input into how something changes, they're more likely to make it work — and the end result is usually better for it.</p>
</div>
</article>
<article class="card">
<p class="card-tag">Coaching · succession</p>
<h3>The people at the center</h3>
<p>One-to-one coaching for the people carrying the weight: the owner planning his exit, the successor stepping into big shoes, the veteran working out what it means to let go. Booked one session at a time — as many as the work calls for — around your calendar.</p>
<p class="outcome">The people at the center don't crack under it.</p>
<article class="work-item">
<div class="work-head">
<h3>The process that could work better</h3>
<p class="work-deliver">Delivered through structured working sessions, with the right people in the room.</p>
</div>
<div class="work-body">
<p>Sometimes the real opportunity isn't getting people to accept a new tool — it's rethinking how the work actually happens. Not patching the old process with something faster on top of it, but asking whether it still makes sense for the people doing it and the customers depending on it.</p>
<p>We facilitate that redesign work with the people closest to the process: mapping how it really works now, where it breaks down, and what a better version could look like. The output is something the team helped build, which is most of why it gets used.</p>
</div>
</article>
</div>
<p class="reassure">Every engagement is built around coordinated hours — never a stretch of days that swallows your week.</p>
<p class="reassure">Most engagements draw on more than one of these. A knowledge holder who won't quite let go is also a team-alignment question; a process redesign that doesn't involve the people doing the work tends not to stick. We design each engagement around what's actually needed — not a fixed program.</p>
</div>
</section>