Q: Provide an example of a time when you requested more information or declined to make a decision without more information.
The software industry, due to its inherent rapid changes in technology and shifting project priorities, has much ambiguity. It is a rare circumstance where a problem and its associated decision and resolution are clearly defined and remain unchanged. In these circumstances where a decision is pending, but not imminent, I prepare for the most likely options. I engage many key stakeholders to understand the situation. I proactively consider my options and the potential impact on my team.
I‘m a documentation team liaison to a product strategy team. I am also a writer on this team. The product ship date appeared to be postponed from the original date. I proactively queried the strategy team about this potential date change. I wanted to provide an alternative ship date to my team. The strategy team did not provide a date change. So, my team prioritized our work and prepared for the original date. It is never too early to proactively prepare for change, even if the change never occurs.
At times, it is important to request more information before making a decision. For example, as Track Manager of Mobile Content for STC Summit 2014, I requested guidelines to help my team review proposals. Summit leaders developed a checklist and distributed it to reviewers. Requesting more information provided the team with a common basis for reviews that will benefit reviewers and conference attendees.