You've hired smart people, and you've invested in tools. You've also restructured more than once. Given all these, on paper, everything should work. But the reality is different. Decisions take longer than they should, and ownership gets blurred. Teams move, then stall, then circle back. You step in more than you want to, not because you enjoy it, but because progress depends on you doing so.
Here's the good news: writing isn't a talent. It's a skill. And skills respond to the same cure as every other skill: reps. Not glamorous reps. Not the kind that gets applause. The kind you do in small rooms, when no one is watching, when you're a little uncomfortable, when you want to quit halfway through because the sentence you just wrote feels like wet cardboard. That's the work.
Most design problems aren't 'design' problems. They're 'Thinking' problems.They're 'Clarity' problems.They're 'Too-many-tabs-open' problems. More prototyping. More pixel-shifting. More polish in Figma alone isn't going to help you with those. For me, without clear thinking, Figma just results in more confusion, more mess, and more mockups than I can mentally manage. The Problem: Figma wasn't the bottleneck - my thinking was
Instructional Designers often prioritize trendy jargon and intricate frameworks over learner clarity, leading to courses that may be polished but fail to deliver understanding.
