domagoj
2025/12/20
5 / 5
Working Backwards has been hugely helpful in my day‑to‑day work because it forced me to slow down and define success before touching any code. The book shows how Amazon starts from a clear, customer‑centric vision expressed in a press release and FAQ, then works backwards to the required features, user experience, and internal capabilities. Applying this, I now invest more time clarifying the target customer, their problem, and the desired outcome; as a result, my projects ship with fewer reworks and stakeholder surprises.
Working backwards is so important because jumping straight into coding optimises for output, not impact. You risk building elegant solutions to the wrong problem, accumulating tech debt and misaligned features. By contrast, the PR/FAQ approach forces tough trade‑off decisions early, exposes unclear thinking, and aligns everyone on what “good” looks like before effort is spent. For me, that mindset shift has been the real value of the book.
