Technical Sounding-Board Hours

A standing block for thinking through technical ambiguity together. The team brings a half-formed problem; you ask more than you answer; they leave owning the direction. No deliverable expected.

What it is

This is the sounding-board pilot named in the intro: a standing block where engineering serves as a sounding board for teams working through technical ambiguity — sometimes the value is just talking the problem through with someone who’s seen it before.

The value isn’t an answer. It’s the thinking — a team working through a problem that’s still half-formed, with someone in the room who’s seen the shape of it before. There’s no deliverable. The team leaves with sharper thinking and a direction they own, not a recommendation you handed down.

How you run it

Hold a standing block, or run it async when scheduling won’t cooperate. It’s a sibling to office hours on the calendar — a known, protected time — but it does a different job, and keeping the two distinct is most of what makes this pilot work.

The key distinction is what the team brings and what it leaves with. Office hours: bring a question, get an answer or a route. Sounding board: bring ambiguity, think it through together, leave with your own thinking sharpened. One is for problems that have an answer; the other is for problems that don’t have one yet.

Aspect	Office hours	Sounding board
You bring	A specific question	A half-formed problem or a decision you’re stuck on
You leave with	An answer or a route to deeper help	Sharper thinking and a direction you own
Engineering’s role	Answer or route	Listen, ask, reflect — help you think
Deliverable	An answer or next step	None expected

Notice that the sounding-board column never promises an answer. That’s the whole point — if a team needs an answer, send it to office hours; the sounding board is for the problems where the work is the thinking, and pretending otherwise turns it back into a consult.

What you commit to is the time and the stance: you’ll show up, and you’ll resist solving it for them.

Templates

Standing this block up is mostly about setting the expectation: this is for working through ambiguity, not for getting an answer. These are the copy-paste starters that carry that expectation into the calendar. Swap anything in [brackets] for your specifics, and replace [#channel] and [video link] with whatever your team already uses. The wording is doing work — it keeps the block distinct from office hours, so keep the intent when you edit, not just the structure.

Launch email

The first announcement. Send it to the deployed teams a few days before the first block. The job of this email is to say what the block is not as clearly as what it is.

Subject: New: weekly Technical Sounding-Board Hours, starting [date]

Hi all,

Starting [date], I'm holding a weekly Technical Sounding-Board Hour — a
standing 45-minute block for thinking through a technical problem that's
still messy. Bring something half-formed: a decision you're stuck on, an
approach you can't quite commit to, a tradeoff you keep circling.

This is not office hours. If you have a question with an answer, take it
there — you'll be out in five minutes. This block is for the problems that
don't have a clean answer yet, where the useful thing is to think it through
out loud with someone who's seen the shape of it before.

  When:  every [day], [start]–[end] [time zone], starting [date]
  Where: [video link] (calendar invite to follow)
  Async: [#channel] — if the time doesn't work, post the problem there and
         we'll work through it in thread.

You won't leave with a recommendation from me. You'll leave with your own
thinking sharper and a direction you can defend — one that's still yours.

See you [day],
[your name]

Notice the email refuses to promise an answer and says so twice. The block only works if teams arrive expecting to think rather than to be told — and they leave owning the direction precisely because you never offered to own it for them.

Calendar invite

Make it recurring at the same time every week. The body should still make sense to someone who finds the event cold, months in, and it should still draw the line against office hours.

Title: Technical Sounding-Board Hour (bring an ambiguous problem)

Weekly thinking-partner block for [program] teams. Bring a problem that's
still half-formed — a decision you're stuck on, a tradeoff you can't resolve.
We'll think it through together. You'll leave with your own thinking sharper
and a direction you own, not a recommendation handed down.

This is not office hours. Got a question with an answer? Take it there. This
block is for the problems that don't have one yet.

Can't make it, or in a different time zone? Post the problem in [#channel]
and we'll work through it in thread.

Recurring · [day] · [start]–[end] [time zone] · [video link]
Host: [your name]

Notice the invite names “a direction you own,” not a deliverable. The whole stance is help them think, not think for them — so the standing description has to set that expectation before the session even starts, or you’ll spend the first ten minutes resetting it.

What to bring

A short fill-in the requester completes and sends before the session. Asking for it does two jobs: it makes sure the problem is genuinely ambiguous rather than a question in disguise, and it forces the team to articulate where they’re stuck before they walk in.

Before our sounding-board session, take five minutes on this. Rough is fine —
the point is to arrive having already wrestled with it, not to write a brief.

  The problem, in one sentence:
  [what you're trying to figure out]

  What we've already tried or considered:
  [the approaches on the table, and why none has won yet]

  Where we're actually stuck:
  [the specific knot — the tradeoff, the unknown, the thing we keep circling]

  What a good outcome from this hour looks like:
  [not "the answer" — a direction we'd feel ready to start moving on]

Notice the last line bans “the answer” and asks for a direction instead. This is the guard against talk with no movement — a team that has already named what “unstuck” would look like is one that can leave the session pointed somewhere, not just pleasantly talked-out.

Weekly reminder

A short nudge in the channel the morning of. Low effort, and it keeps the block from quietly becoming office hours by repeating what it’s for.

Sounding-Board Hour today at [time] [time zone] — [video link].

Bring something you're genuinely stuck on — a messy decision, a tradeoff you
can't resolve. Not a quick question (that's office hours); a problem you want
to think all the way through.

Can't make it live? Post the problem in this channel and we'll work it in
thread.

Notice the reminder re-draws the line every week (“not a quick question”) and offers the async option. The distinction from office hours erodes the moment you stop restating it, and a standing block needs an async path so the thinking can still move when the calendar doesn’t.

Routing

When what a team brought isn’t actually ambiguity, route it rather than forcing it through the wrong block. Send this as a follow-up — keeping the block honest about what it’s for is what protects it from blurring into everything else.

Subject: Following up from the sounding board — [topic]

Hi [name],

Good session, and I think I can point you somewhere sharper than this block.

[Pick one:]

— That turned out to be a question with an answer, not an ambiguity to think
  through. Bring it to office hours [day] at [time] / [#office-hours] — you'll
  be unblocked faster there than reasoning it out from scratch.

— You're past the ambiguity now and you've got a concrete design on the table.
  What you want next is a real second opinion on it, not more thinking-out-loud
  — let's put it through a lightweight architecture review. I'll set that up.

Either way, the direction stays yours — I'm just pointing it at the right room.

[your name]

Notice routing is how you defend the block from blurring into office hours. A question with an answer belongs there; a concrete design that needs a second opinion belongs in an architecture review — sending each to its right room keeps the sounding board for the problems that are still genuinely unformed.

How you show up

Be Socratic. Listen more than you prescribe — the first move is to understand the problem the way the team understands it, not to pattern-match to the answer you’d give. Ask the question that makes them see the thing they were circling. The best sounding-board hour is one where the team says “oh” and you barely spoke.

Help them think; don’t think for them. You’ve seen this shape before, and the temptation is to short-circuit to your conclusion. Resist it. A direction they reasoned their way to is one they can defend and extend after you’ve rotated off; a direction you handed them is one that collapses the first time it’s questioned and you’re not there.

What good looks like

The team’s own thinking gets sharper — they articulate the problem better leaving than arriving.
They leave owning the direction, able to explain why, not just what.
You asked more than you answered.
A genuinely ambiguous problem got smaller without anyone pretending it had a clean answer.
The team comes back when the next ambiguity shows up, because the last session was worth it.

Where it goes wrong

Capacity substitution

You become their de facto architect. What started as helping them think turns into you making their technical decisions, session after session — they stop bringing ambiguity to reason through and start bringing decisions for you to make. The tell: the team can’t explain the direction without citing you. Push the thinking back: “what do you think, and why?” A sounding board they reason with is enablement; one that decides for them is you quietly staffing their architecture.

Blur into office hours

The distinction collapses and the block becomes a second office hours — quick questions, quick answers, no thinking-together. It feels efficient and loses the entire reason the pilot exists. The tell: people show up with answerable questions and leave with answers. When that happens, route the question to office hours and reopen the block for what it’s for, out loud.

Talk with no movement

The session is a pleasant conversation that goes nowhere — ambiguity in, ambiguity out, no sharper. Thinking-together has to actually move the thinking. The tell: the team leaves no clearer than it arrived, session after session. Close each hour by asking what’s sharper now and what they’ll try next — not a deliverable, but a direction. If nothing’s moving across several sessions, the problem may not be one a sounding board can help, and naming that is the help.

What it tells us

Recurring ambiguity is a signal with a destination. When several teams keep arriving stuck on the same kind of half-formed problem, that ambiguity is asking to be resolved once and reused — a new doc that takes a position, or a question set that gives the next team a way to think it through without you.

So track the themes. They feed the four questions — an ambiguity that unblocks more than one team is worth canonizing — and a category of ambiguity you keep working through live, that genuinely resists being written down, is a hiring signal: it’s pointing at judgment the bench is short on.