Free DIY Kit — Tier 2: Staff Track

RUN YOUR OWN
STAFF AI HACKATHON

Surface your real AI use cases — from the people already using AI in your business. One half-day. No consultants required.

100% Free. Everything on mattmurphy.ai is free except the community subscription.

YOU'RE IN

Check your inbox. Your Staff Hackathon Playbook is on the way.

Start with Part 1 — the five pre-conditions. If you can't pass the gut-check, the playbook tells you what to fix first. That honesty is the design.

4
Hours
4
Whiteboards
5-7
Prioritized use cases
$0
Cost to run

YOUR TEAM HAS AI IDEAS.
THEY HAVE NOWHERE TO PUT THEM.

Everyone on your team has been quietly experimenting with ChatGPT, Copilot, or Claude. Some have found real shortcuts. Most have no idea what their colleagues are doing. The knowledge is siloed, the experiments are scattered, and nobody has a framework to turn scattered experiments into prioritized, actionable projects.

In Not Murphy's Law, Chapter 6 calls this Shadow AI — the tools your staff are already using that you don't know about. Chapter 7 maps the Hate Drains — where your company bleeds time on repetitive, manual work nobody wants to own. This hackathon surfaces both in a single half-day session.

S.AI

Shadow AI everywhere — your staff is already using AI tools you don't know about, with no shared standards or visibility

?

Leadership wants an "AI strategy" but nobody has surfaced what's actually possible from the people doing the work

50+

Too many AI ideas, no framework to force-rank which ones to pilot first — sticky notes don't count

0

No safe space for staff to admit fears about AI — so the fears show up as quiet resistance instead

The Line That Changes Everything
"No one in this room is getting fired because of what surfaces today. No one is getting hired to replace you. The goal is more output per person, not fewer people."

This is the first sentence in the playbook. If you can't say it honestly, don't run the hackathon. Run a different process to align leadership first. The playbook tells you how.

What's In The Playbook

7 PARTS + 3 APPENDICES. THE COMPLETE SYSTEM.

PART 1

Pre-Work: Self-Discovery

Five pre-conditions that must be true before you schedule anything. Executive air cover, the no-fire line, participant selection (8-12 cross-functional truth-tellers), workspace, and the 5-day synthesis commitment.

PART 2

Environment Setup

What you need: a conference room, sticky notes in four colors, Sharpies, and coffee. What you don't need: software licenses, IT approval, consultants, or pre-reading materials.

PART 3

The Capture System

Four labeled whiteboard zones set up before participants arrive. Each captures a different category of signal — what's already happening, what's wished for, where time is lost, and what could go wrong.

PART 4

The Half-Day Agenda

Four hours, eight blocks. Frame & Inventory, Wishes & Frictions, Risks & Pattern Recognition, Champions & Commitments. Tight on purpose — momentum matters.

PART 5

The Facilitation Plays

Six repeatable plays: The Opening Reframe, The Honest-Use Permission, The Wish-List Unlock, The Friction Elevation, The Fear Naming, and The Champion Conscription. Practice out loud before the event.

PART 6

30/60/90 Operating Rhythm

Days 1-5: synthesis report. Days 6-14: executive review and pilot selection. Days 15-45: 30-day pilots. Days 46-60: wrap and rollout decisions. Days 61-90: second wave and follow-up hackathon.

PART 7

When You Get Stuck

Honest guidance on when to push through internally (most of the time) versus when outside help is genuinely useful. Includes direct contact for Faction if the patterns point to a larger build.

APPENDICES

Templates & Tools

Use Case Capture Card (print one per use case), Participant Invitation Template (send 7-10 days before), and the Synthesis Report Template (5 pages max — resist the urge to make slides).

The Capture System

FOUR WHITEBOARDS. FOUR CATEGORIES OF SIGNAL.

Each whiteboard uses a different color sticky note. Participants write one idea per note. The visual residue is the artifact you photograph at the end.

WHITEBOARD 1 — "WHAT I'M ALREADY USING"

Yellow sticky notes. One per use case. What AI tool? What task? How often? This is the shadow AI inventory — surfacing what's already happening that nobody talks about.

WHITEBOARD 2 — "WHAT I WISH AI COULD DO"

Green sticky notes. No constraints — encourage absurdity. The constraint-free framing is the point. You're not asking what to build, you're asking what to want.

WHITEBOARD 3 — "WHERE WE LOSE TIME"

Blue sticky notes. Company frictions, not personal ones. Where does work pile up? Where do handoffs break? This is the most valuable whiteboard for executives.

WHITEBOARD 4 — "WHAT COULD GO WRONG"

Pink sticky notes. The pressure-release valve. If fears have nowhere to go — job security, customer trust, regulatory — they manifest as quiet sabotage. Give them a wall.

FOUR HOURS. EIGHT BLOCKS. REAL OUTPUT.

0:00 – 0:10 · Welcome
The Line & Ground Rules
Read the no-fire/no-hire line out loud. Frame the day: surface what's happening, what's wasting time, what's wished for. Leadership sees the output — not who said what.
0:10 – 0:30 · Introductions
Round-the-Room: Role + Repetition
Each participant: 90 seconds. Name, role, how long in the seat, and the most repetitive part of their job. That list seeds the rest of the conversation.
0:30 – 1:00 · Whiteboard 1
Shadow AI Inventory
Yellow sticky notes — what AI tools are you using right now? One tool and one use per note. 20 minutes of writing, 10 minutes reading aloud and grouping visually.
1:00 – 1:30 · Whiteboard 2
The Wish List
Green sticky notes — if a magic AI assistant lived in your laptop, what would you ask it to do? No constraints. The unrealistic wishes are the whole value.
1:30 – 2:00 · Whiteboard 3
Where We Lose Time
Blue sticky notes — company frictions, not personal ones. Where does work pile up? Where do handoffs break? Where do we do the same thing twice?
2:00 – 2:20 · Whiteboard 4
What Could Go Wrong
Pink sticky notes — fears about AI deployment. Don't defend or argue. The job is to capture them. Give the skeptics a wall.
2:20 – 3:00 · Synthesis
Pattern Recognition
Walk all four whiteboards together. Look for clusters (same use case across roles), overlaps (wishes matching frictions), and shadow wins (what's already solving something). Red marker for circles and arrows.
3:00 – 4:00 · Commit
Champion Selection & Next Steps
Select top 5-7 use cases. Fill out a Use Case Capture Card for each — named champion, 30-day pilot description, success criteria. Photograph all whiteboards. Synthesis report lands in 5 business days.

DIY OR FACILITATED?

DIY Hackathon

FREE
  • Full 7-part playbook + 3 appendices
  • 4-whiteboard capture system
  • 6 facilitation plays
  • Use Case Capture Cards
  • Synthesis report template
  • 30/60/90 operating rhythm
  • Self-guided — your champion runs it
Get the Playbook — Free

Facilitated Hackathon

$5,000
  • Everything in DIY, plus:
  • Matt or Faction team on-site
  • Expert facilitation & energy management
  • Real-time coaching during synthesis
  • Executive readout & strategic framing
  • Best for 8-25 participants
Book at Faction →

FROM THE BOOK: NOT MURPHY'S LAW

Whiteboard 1 is the Shadow AI audit from Chapter 6 — surfacing what your staff is already doing that you don't know about. Whiteboard 3 is the Hate Drain inventory from Chapter 7 — mapping where your company bleeds time. The prioritization framework in Hour 4 borrows the read-the-financials discipline from Chapter 9. The hackathon is where the book's frameworks hit your actual org chart.

Read more about the book →

YOU SURFACED THE USE CASES.
NOW BUILD THE CAPABILITY.

The Hackathon Kit is Tier 2 of The Faction certification path. You've surfaced and prioritized — now decide: land the pilots or expand into builds.

Vibecoding DIY Kit

Tier 3: Builder track. Take the use cases your champions surfaced and build them. Pre-Work through production readiness — the full deployment system.

Get the Vibecoding Kit →

The Faction Community

Office hours, deep dives, deployment support, and the certification path from Associate to MADE. $77/mo for the first 90 days.

Explore The Faction →

Faction Facilitated

Need an outside voice? Faction runs facilitated hackathons ($5K), Vibe Code Finisher builds ($8K), and executive briefings. Project-bounded, fixed-scope.

Visit Faction Group →

STOP TALKING ABOUT AI.
SURFACE WHAT'S ALREADY HAPPENING.

Download the playbook, pass the five pre-conditions, pick a date, invite 8-12 truth-tellers. In four hours you'll walk out with a prioritized list of AI use cases, named champions, and 30-day pilot plans.

Prerequisite kits: 30-Day AI PrescriptionBertha DIY Kit → Hackathon (you are here)

YOU'RE IN

Check your inbox. Your Staff Hackathon Playbook is on the way.

Start with Part 1 — the five pre-conditions. The hackathon will fail in predictable ways if any of them aren't true. The playbook tells you exactly what to check.

Explore The Faction Community →

Common questions

QUESTIONS PEOPLE ACTUALLY SEARCH

What is an AI hackathon for staff?

A facilitated half-day to full-day format that surfaces what your floor already knows about AI leverage. The Hackathon DIY Kit includes hour-by-hour methodology, gamification, the Love/Hate Map, and the Three-Bucket Sort—so leadership sees real opportunities, not slide-deck guesses.

Is shadow AI covered in the free frameworks?

Yes. Shadow AI—employees using unapproved AI tools—is addressed in the Hackathon DIY Kit and throughout Not Murphy's Law. For enterprise governance and detection in regulated contexts, Faction Group partners on Olakai deployments at gofactiongroup.com.

When should I use the free kits vs hire Faction Group to build?

Use the kits when you or your team can execute with guidance. Hire Faction when you need production software shipped in modular slices—rapid MVP, R.A.P. automations, vibe-code finishing, or full-stack platforms—with demo cadence and fixed modules instead of open-ended backlogs.