I can do the design work — why can't I tie it to the business?
You can execute. Give you the brief, you deliver the screens, the flow, the polish. But ask why it matters to the business, and you stall. This is not a private failing. Most teams treat the business case as someone else's department — the manager's, the strategist's, anyone's but yours. Look at this honestly. The habit you have is: open the tool, solve the visible problem, ship. The habit you lack is: before that, write down what changes in the world if this ships, in numbers a business cares about. That sentence is missing, not your intelligence. You do this work with others. Use that. A team that asks each other "what does this move" before every task builds the muscle faster than any one person alone. Make the question public, not private.
The gap is not skill. It is order. You open the design tool before you name what it must move. Fix the order: write one sentence — what number this changes, and how — before any screen exists. Do it together, out loud, every time. The link is a habit you build, not a talent you lack.
What changes unlock by starting
- You can state, in one sentence, how any task you're given connects to a real goal.
- Your team stops outsourcing 'the business case' to one person and starts asking the question together.
- You catch disconnected work in review, before it ships, not after someone else notices.
- Meetings shift from defending your work to explaining its purpose — a different, stronger position.