This post is a replay from issue #4 of The Playbook that I never sent to your inbox. I'm on a break from writing new posts, but I'm excited and looking forward to sharing further insights soon. Additionally, I'm making progress with my upcoming handbook about deliberate practice for designers. Some free slots are still available if you're interested, as I plan to charge for them once it's published.
Do you remember the last time your design encountered technical challenges from the engineering side?
The current data structure didn't correspond to the content you had in mind.
The third-party integration didn't support the specific data/information you needed.
The basic development package was limited in creating the experience you designed.
You collaborated with engineers to shape the best possible idea within all constraints. That's good. However, sometimes your teammates disagreed with what you had been designing.
For next time, why don't you take a stance? Disagree with them—with respect, of course.
Push your idea—even just a little bit.
Strengthen your reasons. Is your solution worth the effort and time? Why?
Go even further. What evidence could you bring to convince others?
Engage with tactics. Is it possible to break down the idea into smaller parts for quick wins? Is there a way to seek validation before committing to something bigger?
Technical constraints and challenges are real, and they will always exist.
It's important to stay flexible and adaptable but keep your eyes open—there may be opportunities to push your idea, even just a little.
I'm writing two handbooks to guide designers with valuable insights, helping them thrive in their craft.
Frameworks for Thinking offers various frameworks and tools to help designers and creatives think critically, generate new ideas, and solve complex problems.
Deliberate Practice for Designers provides guides and insights to help you master your craft and become a lifelong learner through deliberate practice.