IMPACT HACKERSWET / Time
03THE TIME LEG / CALENDAR + COMMITMENTS

Unf%ck Your Calendar

Your calendar is a strategy document. Make it tell the truth.

A practical team workshop for turning a crowded calendar into an honest operating plan—with protected priorities, realistic buffers, and meetings that earn their place.

Focused session or Connected series Remote or in person Personal reply within two business days

BUILT FOR A SAFE WORKING ROOMUnpredictability is treated as a design constraint—not a failure to plan perfectly.

THE CALENDAR RESET
FROM FULL CALENDARS TO INTENTIONAL CAPACITY
TIME IS ALREADY SPOKEN FORPRIORITIES HAVE SOMEWHERE TO LIVEA 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.

A calendar can be completely full and still leave no room for the work that changes the outcome. Capacity gets promised before priorities get protected.

The goal is not a perfectly optimized week. It is a calendar that makes tradeoffs visible before reality makes them for you.

The important work is always expected to happen between meetingsEvery open block becomes available to someone elseMeetings multiply while decisions and ownership stay fuzzyThe week has no buffer for transitions, interruptions, or recovery

Leave with a system you can use the next day.

The workshop turns shared frustration into explicit decisions, usable language, and one credible experiment.

01

A calendar baseline

A visible read on where capacity currently goes and which commitments create the most friction.

02

Protected priority space

Real blocks for the work that must move—not a wish list waiting for spare time.

03

Meeting rules

Shared standards for when a meeting is useful, who needs to attend, and what decision it serves.

04

An honest default week

A repeatable starting structure with buffers, boundaries, and room for the unpredictable.

A new meeting request lands on a protected block.

Instead of treating open time as automatically available, the owner can see the tradeoff and use shared language to move, shorten, decline, or redesign the request.

WHAT WOULD COUNT AS EVIDENCEThe difference is visible when priority work keeps a credible place in the week and the cost of moving it is named before the calendar changes.
TIME LEG / DESIGN RECEIPT

Priority work can be protected before availability gets claimed.

The protected-week map makes focus, coordination, buffers, and recovery visible together. Conflicts surface while the team can still negotiate them.

Evidence boundary: this is a claim about the workshop artifact’s intended use, not a quantified client outcome.

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.

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.

01STAYS PRIVATE

Personal circumstances, protected details, and private appointments

02MAY BE SHARED

Capacity constraints, meeting friction, and scheduling patterns

03THE TEAM DECIDES

Priority blocks, buffers, meeting rules, and boundary language

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

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.

01
SEE IT

Read the real week

Inspect the current calendar as evidence of priorities, constraints, coordination, and hidden work.

02
NAME IT

Name the tradeoffs

Decide what must be protected, reduced, delegated, redesigned, or removed.

03
BUILD IT

Build a credible week

Place consequential work, collaboration, maintenance, buffers, and recovery into one honest system.

04
KEEP IT

Protect the change

Create the boundary language and team norms required to keep the new calendar intact.

THE TAKEAWAY ARTIFACTWET / TIME

Your calendar protection plan

Current-week capacity map

Protected priority blocks

Meeting and scheduling rules

One redesigned default week

Built from your context—not downloaded from a generic template.

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 session
WORK 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.

Useful when the people in the room can change the system.

A GOOD FIT

The calendar is full but meaningful progress keeps slipping

Meetings and availability norms are consuming deep-work capacity

The team can make real scheduling tradeoffs

Participants are willing to work from an actual week—not an idealized template

PROBABLY NOT THIS WORKSHOP

The team has no authority to change any calendar commitments

The desired answer is simply to fit more into the same capacity

The central issue is a labor, accommodation, or clinical concern requiring specialist guidance

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 Calendar

We are considering Unf%ck Your Calendar, a facilitated team working session focused on the Time leg of our operating system. The session would help us work on a familiar pattern: A calendar can be completely full and still leave no room for the work that changes the outcome. Capacity gets promised before priorities get protected. The intended output is your calendar protection plan, 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 brief

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.

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 time blocking?

Time blocking is one tool, not the workshop. The deeper work is deciding what deserves protection, designing credible capacity, and creating agreements that let the calendar hold.

02Does everyone leave with the same ideal week?

No. Roles, constraints, energy, and control differ. Participants use a shared method to build calendars that are individually credible and mutually compatible.

03Can this work for a team with unpredictable demands?

Yes, when unpredictability is treated as a design constraint. The workshop makes room for buffers, response windows, and escalation rather than pretending interruptions will disappear.

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 TIME LEG?

Make your calendar tell the truth about what matters.

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