Weakness 3-Step Answer Templates

The thing I've been working on most is getting better at delegating. I have a tendency to hold the hardest pieces of a project on my own plate because I want them done a specific way. [Evidence: one specific moment - a project where this cost you time, momentum, or an outcome.] What I've done about it: I started building explicit delegation maps at the start of every project - what's mine, what's the team's, what's negotiable. [Add a specific result: team speed, a moment you took time off without the work stalling, an outcome metric.] It's still an active muscle. But the pattern is meaningfully different than it was a year ago.

My real weakness is that I used to save feedback for formal moments - reviews, check-ins, end-of-project recaps - instead of giving it in the moment. [Evidence: a specific example where the delay cost you or the team.] What I've changed: I built a habit of giving one piece of real-time feedback in every meeting I run. [Result: team speed, a specific relationship improvement, or a cultural shift you've measured.] It's still awkward sometimes. But the cost of saving feedback was bigger than the discomfort of giving it live.

Something I've actively worked on is sitting with ambiguity before forcing a decision. My instinct used to be to move fast and commit, even when the picture wasn't complete. [Evidence: a specific decision you rushed and later regretted.] What I've built: a two-day minimum between the moment I feel ready to decide and the moment I commit, for decisions above a certain size. [Result: a decision you got right because you waited.] I still make fast calls when the situation demands it. But I've stopped confusing speed with clarity.

The real weakness I've been working on is saying no to scope creep. I used to absorb new requests into a project mid-flight rather than naming the trade-off. [Evidence: a project where creep pushed a launch or burned the team.] What I've been doing: I now surface the trade-off explicitly whenever new scope lands. [Result: a specific moment where surfacing the trade-off saved the project timeline.] It's harder than just saying yes. It's also how the team I'm on ships on time now.

Something I've actively invested in is presenting up to senior leadership. My instinct was to over-explain the work rather than lead with the punchline. [Evidence: a specific presentation where the message got lost in the detail.] What I've changed: I now build every exec presentation top-down - the punchline first, the supporting data second. [Result: a specific moment when senior leadership made a faster decision because of a tighter deck.] It took deliberate practice. It's changed how I think about communicating at every level.