Every feature has a cost—usually in time or technical debt. Instead of asking "Can we do this?", ask "What are the trade-offs if we prioritize this?"
Context-switching is a productivity killer. If a dev has their headphones on and is deep in the zone, try to batch your questions for a scheduled sync or an asynchronous Slack message rather than tapping them on the shoulder. Playing Well with Others: Your Field Guide to D...
Borrowed from improv, this means leaning into the story the DM and other players are building. If the party wants to investigate the spooky cave, don’t be the person who insists on staying at the inn to "save money." Every feature has a cost—usually in time or technical debt
Software development is a team sport. When you treat developers as creative partners rather than "feature factories," the product (and the office vibe) improves instantly. Borrowed from improv, this means leaning into the
Developers are natural problem solvers. Instead of saying "Move this button two pixels left," explain the user friction you're trying to solve. You might get a better technical solution than the one you imagined.