Primary source
How to Do Great Work Without Being an Asshole
book_cube summary post pair with practical notes from both parts [1/2] and [2/2].
Primary source
How to Do Great Work Without Being an Asshole
book_cube summary post pair with practical notes from both parts [1/2] and [2/2].
How to Do Great Work Without Being an Asshole
Authors: Paul Woods
Publisher: LID Publishing
Length: 2019
Paul Woods outlines pragmatic management for creative environments: strong outcomes without toxic behavior, process chaos, or normalized burnout.
Original
TranslationManagement / Leadership / Process / Communication
How to Do Great Work Without Being an Asshole is a compact operating guide for leaders who must keep quality, speed, and healthy team culture at the same time.
1. Book map (14 chapters)
Chapters 1-2. Culture and ego
Long-term success comes from a strong culture and reputation, not toxic behavior. A leader's job is to grow the team, not personal ego.
Chapters 3-7. Operating discipline
Fewer but sharper meetings, honest pitching, clear planning, structured briefs, and timely feedback.
Chapters 8-12. Client and career practice
Presentations as transparent reasoning, reduced crunch, honest client collaboration, thoughtful hiring, and respectful exits.
Chapters 13-14. Tough calls and manifesto
Leaders sometimes need unpopular decisions to protect outcomes. High standards should not be confused with toxicity.
2. Core thesis
Being "hard on standards" and "respectful with people" is not a trade-off. Woods clearly separates high expectations from abusive behavior. The first drives outcomes, the second erodes trust, employer brand, and long-term team performance.
3. Practical operating tools
Meeting checklist
- Define the meeting goal in one sentence.
- Invite only people required for the decision.
- Start with context and expected outcome.
- Facilitate discussion and protect agenda focus.
- Close with next steps, owner, and deadline.
- Send notes right after the meeting.
Client briefing template
- Task context and constraints.
- Single-sentence project description.
- Business outcomes this project must support.
- Expected deliverables and artifact format.
- Interim and final deadlines.
- Links to source files, docs, and access.
4. Client collaboration and pitching
The book criticizes unpaid pitch contests because they reward superficial performance instead of real collaboration quality. A stronger alternative is a shared demo-day format where client and agency solve real problems together and evaluate working dynamics directly.
5. Feedback and difficult decisions
Feedback must be direct, specific, and timely, but still respectful. At the same time, leaders cannot hide behind false politeness when quality, deadlines, or role fit require tough calls.
6. Common anti-patterns
Treating tough decision-making as permission to disrespect people.
Running meetings without goal, context, and explicit outcomes.
Normalizing unpaid pitch work as a default commercial model.
Replacing honest status updates with polished storytelling.
Ignoring early crunch signals and team overload.
Hiring on promises while skipping culture and ethics red flags.
7. Recommended patterns
Build team reputation on respect, transparency, and delivery quality.
Treat meetings and presentations as management artifacts, not rituals.
Standardize briefs and feedback in a written shared template.
Work with clients as part of the team, not as external judges.
Treat overtime as an exception and fix root causes.
Handle hiring and exits in ways that preserve relationships and trust.
8. 30-day rollout plan
- Week 1: introduce shared templates for briefs and meeting notes.
- Week 2: clean team calendars and remove meetings with no concrete output.
- Week 3: upgrade feedback quality and client presentation structure.
- Week 4: run a retro on crunch, hiring quality, and process red flags.