A triage rule
A simple way to distinguish information, decisions, delegated work, and action you own.
IMPACT HACKERSWET / Work
01THE WORK LEG / EMAIL + INTAKE
Unf%ck Your Inbox
Your inbox is an intake system. Make every message earn a route.
A practical team workshop for turning email from a source of interruption, ambiguity, and accidental commitments into a work intake system people can actually trust.
Focused session or Connected series Remote or in person Personal reply within two business days
BUILT FOR A SAFE WORKING ROOMPrivate messages stay private. Teams can work from sanitized patterns without exposing confidential email.
THE INBOX RESET
FROM REACTIVE READING TO DELIBERATE ROUTING
EVERYTHING LOOKS URGENT → EVERY MESSAGE HAS A ROUTEA working preview of what the team builds together.
THE WET METHOD
Work, Energy, and Time form one operating system. Improve one leg without ignoring the other two. Compare the full method.
THE REAL PROBLEM / 01
The inbox is not just communication. It is where requests, decisions, obligations, and other people’s priorities quietly enter the work.
The goal is not inbox zero. It is inbox clarity: every meaningful message has a known next move, owner, or place to live.
Important messages disappear beneath low-value trafficEmail becomes a task list nobody intentionally designedResponses create commitments without clear ownershipPeople keep checking because they do not trust what happens when they stop
WHAT CHANGES / 02
Leave with a system you can use the next day.
The workshop turns shared frustration into explicit decisions, usable language, and one credible experiment.
A response rhythm
Clear expectations for when email is checked, answered, escalated, or moved elsewhere.
A commitment boundary
Language for acknowledging a request without silently accepting its deadline or priority.
A cleaner handoff
Shared rules for what belongs in email—and what belongs in a task, meeting, document, or conversation.
THE NEXT MONDAY / FIELD NOTE
A request arrives at 9:12 Monday morning.
Instead of forwarding it, flagging it, and silently carrying it, the recipient names the route: information, decision, delegated work, or action they own.
WHAT WOULD COUNT AS EVIDENCEThe difference is visible when the request has an owner, an explicit next move, and no accidental promise hiding inside the reply.WORK LEG / DESIGN RECEIPT
A request can be seen without becoming an accidental yes.
The routing tree separates acknowledgment from commitment. The team can name whether a message is information, a decision, delegated work, or an action—and decide where it belongs.
Evidence boundary: this is a claim about the workshop artifact’s intended use, not a quantified client outcome.WHY IMPACT HACKERS
Make the decision visible enough to survive Monday.
We use the team's real patterns, make the operating decision together, and leave that decision inside a shared artifact—not in a slide deck everyone forgets.
A SAFE WORKING ROOM
Privacy is part of the workshop design.
People should not have to expose personal material to improve a shared system. The boundary is explicit before the work begins.
Message contents, confidential threads, and personal inboxes
Sanitized patterns, channel friction, and handoff examples
Routing rules, response norms, and escalation paths
“Teams rarely need more pressure to perform. They need a clearer operating agreement they can actually keep. My job in the room is to help make that agreement visible, usable, and honest.”
Devin Shea · Impact Hackers
THE WORKING SESSION / 03
Less advice. More contact with reality.
We use the team’s actual patterns, constraints, and examples. The system gets tested while everyone who must live with it is still in the room.
SEE IT
Expose the hidden work
Map how messages become decisions, tasks, interruptions, and commitments in the current system.
NAME IT
Build the routing rules
Create a small decision tree for delete, delegate, defer, decide, and do.
BUILD IT
Practice on reality
Use real inbox patterns to test the rules and find the exceptions that matter.
KEEP IT
Set the agreement
Leave with personal and team norms that make the new behavior safe to maintain.
THE TAKEAWAY ARTIFACTWET / WORK
Your inbox operating agreement
Message triage decision tree
Response-time expectations
Escalation and channel rules
One concrete inbox reset experiment
WHAT SURVIVES / 04
A workshop is only useful if Monday behaves differently.
The artifact records the rules, boundaries, and experiment the team chose. It gives the change somewhere visible to live after the room clears.
Shape the right working sessionWORK WITH THE METHOD / INTERACTIVE LAB
Touch the operating decision before you book the room.
These examples use invented, non-sensitive patterns. Nothing is uploaded or saved.
FIT / 05
Useful when the people in the room can change the system.
A GOOD FIT
Email is creating constant low-grade urgency
Important work enters through too many informal channels
The team wants shared rules, not another personal productivity trick
Participants can bring real examples and change how work is routed
PROBABLY NOT THIS WORKSHOP
You only want a list of app shortcuts
Leaders will not honor the communication agreements
The underlying issue is harassment, legal discovery, or records compliance
MAKE THE CASE INTERNALLY
Give the person who owns the decision something useful to forward.
This brief describes the operating problem, intended artifact, and scoping boundary without turning the workshop into a vague culture pitch.
INTERNAL DECISION BRIEFUnf%ck Your Inbox
We are considering Unf%ck Your Inbox, a facilitated team working session focused on the Work leg of our operating system. The session would help us work on a familiar pattern: The inbox is not just communication. It is where requests, decisions, obligations, and other people’s priorities quietly enter the work. The intended output is your inbox operating agreement, plus one bounded experiment we can observe in the work afterward. Format, participant needs, and investment would be scoped before any commitment.
Plain text · No tracking in the copied briefTHE COMPLETE STOOL / 06
Three workshops. One operating system.
Start with the leg creating the most friction or combine the series into a broader Work, Energy, and Time reset.
QUESTIONS / 07
Before we put it on the calendar.
Format, participant count, and investment are scoped around the people, context, and change the session needs to produce.
01Is this an inbox-zero workshop?
No. A low message count can feel satisfying without improving the work. We focus on trusted routing, explicit commitments, and useful response norms.
02Do we need to use a specific email platform?
No. The operating rules work across common email tools. Platform-specific setup can be incorporated when it helps the team apply the decisions.
03Will participants have to share private messages?
No. People can work with sanitized patterns or examples. The workshop does not require exposing confidential email.
04Who facilitates, and how tailored is the session?
An Impact Hackers facilitator leads the session. The examples, working artifact, and exercises are shaped around the team context you share before the workshop; the operating principles stay consistent.
05What does the investment process look like?
There is no payment on the inquiry form. We first confirm fit, format, participant needs, and delivery constraints, then share a scoped recommendation before you make a commitment.
06What happens after the workshop?
The team leaves with its working artifact, one bounded experiment, and an explicit way to notice whether the new agreement is changing Monday—not just whether people enjoyed the session.
READY TO RESET THE WORK LEG?
Stop letting every message become an invisible promise.
Tell us who is in the room, what keeps happening now, and what would need to be different afterward.
Start the workshop conversationPersonal reply within two business days · No payment today