Participants work in small groups from the same fictional project case. Everybody gets the same fucking project. What they do with it may not be the same.

First, groups map the whole transaction behind the visible project outcome: who benefits, who performs the work, who makes decisions, where costs land and who carries the consequences.

Then they follow the cost.

Did an apparent project efficiency actually eliminate a resource demand? Reduce it? Transfer it to another person or team? Defer it into the future? Convert it into another kind of cost? Hide it from the formal project account?

Or do we simply not fucking know?

Then we compare the maps.

What did one group notice that another didn't? What did participants treat as established fact? What did they infer? What information did they fill in because the story seemed obvious? What disappeared because nobody thought to count it?

The project case becomes a way to examine both the transaction and the humans examining the transaction.

The objective is not to manufacture a predetermined answer about what the organization should do next.

It is to make more of the actual transaction visible—and to distinguish what the available information establishes from the stories humans build around it.

The first job is simpler: Put the fucking cost on the map.

The workshop draws from the Honey, You’re Lunch Money™ territory and adapts its investigative methods for group use through The Whole Project Transaction Map™, The Project Cost Movement Map™, and The Evidence-State Overlay™.

Together, the tools help participants map who benefits, performs work, holds decision authority, expends resources and carries consequences; trace whether project costs or resource demands were eliminated, reduced, transferred, deferred, converted, hidden or unmeasured, newly created, or remain unknown; and distinguish what is observed, agreed or documented, inferred, or unknown.

Because groups work from the same project evidence, the maps themselves become part of the investigation. Participants can compare what different groups noticed, omitted, interpreted or storied—and examine how the account of a project changes depending on what humans decide counts.

The larger HYLM territory investigates hidden work, transferred cost, responsibility without authority, competence consumption, urgency cultures, stress, burnout and the ways apparently functional systems can become dependent on human capacity they never formally accounted for.

This is not a workshop about proving that every difficult project is exploitative or that every invisible contribution is inherently unacceptable.

Sometimes humans knowingly choose costs. Sometimes the return matters. Sometimes no preferable alternative exists. Sometimes the arrangement is still worth it.

The first job is simpler: Put the fucking cost on the map.

Participants leave with a practical way to build a more complete account of what a project actually required—not merely what appeared in the official project record.

They will have practiced how to:

• Map the whole project transaction — identifying who benefits, performs work, holds decision authority, expends resources and carries consequences, including contributors and resource pools outside the obvious project boundary.
• Follow the fucking cost — distinguishing whether a resource demand was eliminated, reduced, transferred, deferred, converted, hidden or unmeasured, newly created, or simply cannot be determined from the available evidence.
• Separate evidence from story — distinguishing what is observed, agreed or documented, inferred, and genuinely unknown rather than unconsciously filling gaps in the account.
• Recognize snormalized™ costs — costs that may be visible in the evidence but have become so ordinary that humans stop registering them as information worth examining.
• Notice human capacity as a project resource — including time, attention, coordination, technical and operational capacity, personal time, household capacity, displaced work and future work that may contribute to a project outcome without appearing as formal project resourcing.
• Interrogate their own capacity assumptions — including what they mean when they say “I’ve got it,” “I can absorb it,” or “we’ll make it work,” and whether the resulting resource transaction has actually been represented in the project account.
• Work comfortably with unknowns — because an incomplete account does not become more accurate by inventing the missing fucking data.

Participants do not leave with a prescribed judgment about whether a project, tradeoff or human contribution was acceptable.

They leave better equipped to see the transaction before deciding what the transaction means.

The project may have been successful.
The trade may have been worth it.
The human may have chosen it.
The cost still fucking existed.

Put the fucking cost on the map.