Skip to content

Good reads: Solving a problem

Various ways to think about approaching a problem

Old School Burke
Old School Burke
1 min read

Let's talk about solving a problem. How you think about solving a problem, the ways you approach, the lens you use to view it has an impact on the solution of the problem itself. Here are some reads to add to your problem-solving toolkit.

Generated with: Illustration of a modern navigational theme with digital interfaces, satellite imagery, and GPS markers. The central focus is a glowing compass, guiding the viewer through various challenges and obstacles, representing the navigation through problems to reach solutions.
  1. Completed Staff Work: The Art of Problem-Solving: Learn about the concept of Completed Staff Work (CSW) in solving problems comprehensively, ensuring all facets are addressed before decisive actions are taken.
  2. 30 Ways to Think About a Problem: Marcus shares 30 perspectives to refine your approach towards problem-solving. His ideas may spark a new way of tackling your challenges.
  3. Don’t Bring Me Problems, Bring Me Solutions: Seth dives into a common managerial mantra and explores why a solutions-only mindset can be limiting.
  4. Avoiding the Hard Problem Trap: The temptation of complex problems is alluring, and they can sometimes deviate teams from the main goals. This post offers insights on aligning your problem-solving journey with the broader mission.

Your feedback is the compass guiding this newsletter. Reach out to me via email.

reads-editionNewsletter

Related Posts

Members Public

010: Don’t Panic: Unblock yourself first

Unblocking yourself is part of the learning journey. When you get stuck, resist the temptation to type “Help!” immediately and run. Try these steps first: * Give your brain a chance to self-solve * Dive into existing docs or knowledge bases * Tinker, test, and experiment * Reach out methodically, with strong context, only

Members Public

009: The Ladder of Autonomy

Understanding Task Relevant Maturity and Ladder of Autonomy

009: The Ladder of Autonomy
Members Public

008: Complete Ownership During Incidents

There’s a constant temptation in our software engineering world to treat incidents as someone else’s problem. When your service experiences downtime because of an infra hiccup, it’s easy to say, “This is Infra's problem,” and then sit back. But if you’re the service owner,

008: Complete Ownership During Incidents