Any advice on how to make quick decisions at a large organization without wasting time discussing possibilities and not getting anything done?

491 views6 Comments
Sort By:
Oldest
Director of Product Management in Services (non-Government)a year ago
Get alignment on where the team should invest it’s time in and define objectives while management giving authority to discover and execute while being directionally aligned. Large organisations have larger stake on the ground and so failure and brand image impact are looked into carefully. While as an agile team we want to fail fast, as a large organisation, we don’t want to fail large.
CPO in Travel and Hospitalitya year ago
I always start with a recommendation.  Have the smallest group possible come up with the "answer" then pose alternatives as "things considered".  It stops from having the larger org / group spend time on 10 alternative paths.  Maybe you have to re-open 1 or 2 of them, but then it is just in comparison to the recommendation.
1
VP of Product Managementa year ago
Having well-thought out options with positives and negatives plus a recommendation can work.  Having something for people to react to can help narrow the conversation quickly vs. an open-ended conversation.  Another idea is to state at the beginning of the meeting that "The goal is to leave here with a decision about ..."

lock icon

Please join or sign in to view more content.

By joining the Peer Community, you'll get:

  • Peer Discussions and Polls
  • One-Minute Insights
  • Connect with like-minded individuals
VP of Product Management in Hardwarea year ago
It starts with setting the right expectations, having clear deadlines, and understanding what the dependencies to that decision is. For example: Do we need experts? Which part of the organization do we need? With products today, there are so many parts that need to come together that depend on what the decision is about. Figuring out who needs to be part of that decision, who needs to build it or participate in the conversation and understanding the organization at large is key. But you also want to limit the number of people involved as you don’t want management that don’t necessarily need to be there to be the bottleneck for decisions. Structure is important 

For day to day decisions, push back on people so that they can make those decisions themselves. Empower people and trust in their knowledge and decisions. 
Senior Vice President of Product Management in Softwarea year ago
Here's a strategy that's worked for me: First, set a clear agenda before any meeting and stick to it. Allocate specific time for discussions and decision-making. Second, empower smaller, cross-functional teams to make decisions; they're often closer to the details and can move faster. Third, adopt a "disagree and commit" philosophy. It's okay for everyone to voice their opinions, but once a decision is made, everyone commits to it. Lastly, always be data-driven. Having clear data points can cut through a lot of subjective debates.

Content you might like

Visionary30%

Communication skills59%

Empathy52%

Accountability38%

Decision-making skills39%

Adaptability20%

Integrity30%

Team-building17%

View Results
35.1k views8 Upvotes1 Comment
CTO in Software12 days ago
A couple of suggestions: 1) You ask coaching questions to assess whether the candidate has critical thinking; 2) Respectfully, you put the candidate under moderate pressure and observe how they react. This might involve saying ...read more
670 views1 Comment

15%

224%

335%

423%

511%

View Results
30.5k views6 Upvotes