220: Ben and Adam Wrap The Year

What It Covers

Ben and Adam close out the year discussing operational strategies for staying lean while scaling: formalizing holiday shutdowns, reducing support volume through FAQ-first design, outsourcing via services over hires, GitHub issue management, implementing Shape Up cycles at Tuple, structured async check-ins, and the case for replacing Twitter with YouTube as a primary content platform.

Key Questions Answered

• •Holiday Shutdown Formalization: Closing the company for the final two weeks of December works best when paired with a tiered autoresponder system — a general "we're closed" message for standard requests, plus a separate urgent-only email address that triggers loud notifications to on-call staff. This structure lets support staff fully disconnect while maintaining a safety valve for genuine server-down emergencies, which historically occur fewer than three times per year.
• •Support Volume Reduction via FAQ-First Design: Rather than hiring more support staff to handle recurring license interpretation questions, add an FAQ section directly to the license page that restates existing terms in plain language. Simultaneously, remove explicit invitations to email — such as "not sure if this is allowed? shoot us an email" — from product pages. Passive discoverability of a support address reduces low-value inbound volume without eliminating legitimate contact paths.
• •Outsource via Services, Not Hires, for Experimental Work: When validating whether a task can be delegated, use fractional service providers rather than full-time hires. The asymmetry matters: ending a service contract carries no ethical weight, whereas hiring someone who then quits their job creates real harm if the experiment fails. Applied examples include QA outsourcing, tier-one support services, VA subscriptions, merch fulfillment warehouses, and one-off team retreat planners found through Twitter.
• •GitHub Issue Management via Default-Close Architecture: A prototype system that auto-closes every new GitHub issue and pull request via webhook, routing them into a private internal triage queue, removes the coercive social dynamic of GitHub's open inbox. Unlike email — where ignoring a message is socially neutral — leaving a GitHub issue open signals obligation. A default-closed model mirrors Apple's bug reporter UX: submitters have no expectation of response, and only triaged-valid issues get reopened publicly.
• •Shape Up with Two-Month Cycles and Linear Tracking: Tuple doubled perceived shipping velocity by adopting two-month cycles aligned to calendar months (January–February, March–April, etc.) rather than strict six-week windows ending on arbitrary dates. Using Linear with explicit due dates, team leads, and project status visible to all gave engineers a persistent mental model of cycle position. Treating deadlines as firm — following up in Discord when a ship date passes — reinforced accountability without requiring formal process overhead.
• •Structured Async Check-ins: Three Questions, Three Days: Replacing daily "what did you work on?" Basecamp prompts with three distinct weekly questions — Monday: what will you complete this week; Wednesday: how are projects progressing; Friday: what did you get done — increased response rates and surfaced blockers mid-cycle. The Monday framing specifically forces engineers to define a completable unit of work, not just an activity, which improves both planning precision and end-of-week satisfaction.