Northwind Labs

Delegation

• Hand them the skeleton of a decision, not the meeting about the meeting.
• Ask for the interface first: what others will inherit when they leave the room.
• Delegate ownership of standards, schemas, and the unspoken load-bearing rules.

Meeting rhythm

• Default to a written brief. If it cannot be read in eight minutes, it is not a meeting.
• Protect a deep-work morning three days a week; status belongs in a log, not a call.
• Review interfaces and edges, never a recap of a recap.

Burnout prevention

• Context-switch weather is the injury. Cap concurrent systems at two.
• Do not park them as the unofficial architecture board for every squad.
• Give recovery as silence and a closed calendar, not a wellness webinar.

Delegation

• Give them the first move on stalled work, then get out of the path.
• Delegate kickoffs, client turns, and any room that has gone cold.
• Pair them with an Architect when a spark has to become a system.

Meeting rhythm

• Keep them to 25 minutes with a live decision. No agenda, no attendance.
• Do not bury them in status theatre; they need a surface to push.
• Call them in at the stall, not at the weekly hour that always happens.

Burnout prevention

• They burn in waiting rooms. Idle process is not rest; it is friction.
• Rotate the firefighting so they are not the only thaw in the building.
• After a breakthrough week, give them a clean day with no inbound.

Delegation

• Send them into frayed collaborations before you send a process doc.
• Trust them with the human weather: onboarding, repair, the quiet check-in.
• Delegate rituals, cross-team translation, and anything that must stay whole.

Meeting rhythm

• Let them host the 1:1 and the repair conversation. Skip them on all-hands panels.
• Prefer a walk or a courtyard to a tiled grid of faces.
• Never stack 'just a quick' at the end of their day — that is when they hold the field.

Burnout prevention

• Do not confuse their calm with spare capacity. Restoration is the work.
• They absorb weather. Name it, and take some of it back.
• Protect a weekly hour that is not for anyone else.

Delegation

• Give them a prototype that should not exist yet, and a boundary of time.
• Ask what two things they would join, not what they would optimize.
• Delegate R&D spikes, naming, and any problem that is still two problems.

Meeting rhythm

• Keep their work slightly private until the material turns. Premature review kills it.
• Time-box a show-and-tell every other week — not a demo every Friday.
• Invite them last, once the question is strange enough to need them.

Burnout prevention

• Continuous critique is the injury. Unfinished rooms must stay unfinished for a while.
• Do not measure them on throughput of tickets; measure the turn in the material.
• Give them a studio hour with the door closed and no Slack.