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."
Don't wait for a sprint retrospective to voice concerns. Build a culture where "that’s not feasible" is the start of a conversation, not the end of one.
Since "D..." could mean a few things, were you looking for a guide to , Developers , or perhaps something else like Designers or Data Scientists ? Playing Well with Others: Your Field Guide to D...
At the end of the day, D&D is about the memories you make with friends. Don't let your "character's personality" get in the way of everyone actually having a good time. Option 2: The Professional’s Guide
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.
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?" Since "D
Here is your field guide to building a bridge instead of a wall: