Question 1
Difficulty: medium
How do you prioritize competing IT demand requests when business units all believe their project is urgent?
Sample answer
I start by getting out of the conversation about urgency and into a discussion about value, risk, and capacity. My first step is to make sure every request has the same basic information: business objective, expected benefit, deadline driver, dependencies, cost, and what happens if we do nothing. Then I work with stakeholders to score the demand against agreed criteria, rather than relying on whoever is loudest. I also look at strategic alignment, regulatory impact, and operational risk, because those usually matter more than short-term pressure. In practice, I’ve found that transparent prioritization reduces conflict a lot. If a request cannot be scheduled, I explain why, offer alternatives, and keep the sponsor informed about what would need to change for it to move up. That way, the process feels fair, not arbitrary.
Question 2
Difficulty: medium
Describe a time when you had to say no to a senior stakeholder who wanted their IT request delivered quickly.
Sample answer
In a previous role, a senior sales leader wanted a customer-facing enhancement pushed into the next release, but we already had a production stability issue and a compliance item that were both higher risk. I knew that simply saying no would not work, so I approached it as a decision based on facts. I walked them through the current backlog, the support impact, the release capacity, and the consequences of delaying the other items. I also showed what could be delivered as a smaller interim change, which would give some immediate benefit without creating delivery risk. The key was staying calm, respectful, and consistent. I didn’t treat it as a battle; I treated it as a portfolio decision. The stakeholder was initially frustrated, but they appreciated the transparency and the fallback option. In the end, we protected the release and still addressed part of their need quickly.
Question 3
Difficulty: medium
What framework or process do you use to assess and triage new IT demand?
Sample answer
I prefer a process that is simple enough for business users to understand but structured enough for IT leadership to trust. Typically, I start with intake through a standard request form or demand log, then check for completeness and whether the request is a true new demand, a defect, an enhancement, or a project dependency. After that, I apply a scoring model based on business value, regulatory or security impact, operational urgency, effort, and strategic fit. I also identify whether the demand can be satisfied by an existing service or whether it needs analysis from architecture, security, or finance. The most important part is not the form itself but the governance around it. I make sure decisions are visible, criteria are documented, and assumptions are reviewed regularly. That keeps the process moving and prevents demand management from becoming a bottleneck or a black box.
Question 4
Difficulty: easy
How do you balance business demand with limited IT delivery capacity?
Sample answer
Balancing demand and capacity is really about making trade-offs explicit. I don’t believe in promising everything and then hoping the team will somehow absorb it. Instead, I keep a current view of delivery capacity by team, skill set, and release window, and I use that to compare incoming demand against what is realistically possible. When demand exceeds capacity, I work with stakeholders to either de-scope, phase, defer, or substitute lower-value work. I also look for patterns in demand, because sometimes multiple requests point to a larger underlying issue that can be solved once instead of three times. Another thing I value is maintaining a small amount of unallocated capacity for urgent operational needs, because a completely full plan usually becomes fragile very quickly. The goal is to protect focus for the delivery teams while giving the business a clear view of when work can actually happen.
Question 5
Difficulty: medium
Tell me about a time you improved the demand management process in an organization.
Sample answer
In one organization, the demand process was mostly email-based, which meant requests were getting lost, duplicated, or approved without enough information. I introduced a more structured intake workflow with clear categories, mandatory fields, and a visible status tracker. That alone reduced a lot of confusion, but the bigger improvement came from defining decision points and ownership. We clarified who could approve what, what information was required before review, and how escalation would work when priorities conflicted. I also built a simple reporting view so leadership could see demand volume, aging requests, approval bottlenecks, and delivery trends. Within a few months, we saw fewer rework cycles and less frustration from business teams because they finally knew where their requests stood. For me, that kind of process improvement is successful when it creates better decision-making, not just more administration.
Question 6
Difficulty: hard
How do you handle demand requests that are strategically important but not yet fully defined?
Sample answer
That happens a lot, especially when the business sees an opportunity but hasn’t translated it into a clear requirement. In those cases, I try not to force the request into a delivery queue too early. Instead, I separate discovery from execution. I’ll work with the sponsor to define the problem, expected outcomes, constraints, and success measures, and I’ll involve the right partners such as architecture, security, or product owners if needed. If the request has strategic merit, I’ll make sure it is visible in the portfolio and assessed alongside other initiatives, but I’ll be honest that it may need a discovery phase before anyone can commit to delivery dates or costs. That approach avoids premature commitments and reduces the risk of rework later. It also helps stakeholders understand that a good demand manager doesn’t just approve or reject requests; they help shape them into something executable.
Question 7
Difficulty: medium
How do you report on IT demand to leadership in a way that supports decision-making?
Sample answer
Leadership reporting has to go beyond listing requests. I focus on trends, bottlenecks, risks, and decision points. For example, I’ll show demand inflow versus delivery capacity, the age of open items, how much demand is tied to regulatory or operational obligations, and where the biggest conflicts are across business units. I also highlight items that need executive intervention, because leadership usually wants to know where a decision is required, not read every detail in the backlog. I like to use a mix of visuals and narrative: a simple dashboard for patterns and a short summary that explains what changed since the last review. The best reports lead to action. If a report doesn’t help leadership reallocate capacity, approve trade-offs, or remove blockers, then it’s just noise. My goal is to make demand visible enough that governance becomes faster and more informed.
Question 8
Difficulty: hard
What would you do if two high-value requests were both competing for the same release window?
Sample answer
I would first confirm whether they are truly competing for the same window or whether one could be split, phased, or moved without meaningful impact. Then I’d compare them using the agreed prioritization criteria: strategic alignment, financial value, risk reduction, compliance need, operational dependency, and customer impact. If both requests score highly and there’s still no clear winner, I’d escalate the decision to the right governance forum with a balanced recommendation rather than letting the conflict drag on. I’d also check whether the delivery team has the right resources and whether sequencing the work differently could reduce risk. The important thing is to avoid making the decision based on who requests first or who has the most influence. I want the outcome to be defensible, documented, and understood by both sponsors. Even when people don’t get the answer they hoped for, they are more likely to accept it if the process is transparent and consistent.
Question 9
Difficulty: easy
How do you work with project managers, architects, and business stakeholders in a demand management function?
Sample answer
I see demand management as a connector role, so collaboration is essential. With business stakeholders, I focus on understanding the real need behind the request and helping them frame it in terms of outcomes rather than just features. With project managers, I make sure demand is translated into realistic delivery plans and that they have early visibility of what is likely to come next. With architects and technical leads, I rely on them to identify constraints, solution options, and long-term implications so we don’t approve work that creates future problems. My style is to keep communication regular and practical. I don’t want demand reviews to feel like a gatekeeping exercise; they should feel like a shared planning conversation. When these relationships work well, the organization gets better prioritization, fewer surprises, and more trust in the process. That’s when demand management really adds value instead of becoming a paperwork step.
Question 10
Difficulty: medium
How do you ensure demand management supports both short-term operational needs and long-term strategic goals?
Sample answer
I make a deliberate distinction between run-the-business demand and change-the-business demand, then manage both within the same overall governance view. Operational requests need enough flexibility to handle incidents, regulatory deadlines, and business continuity issues, while strategic initiatives need space to deliver longer-term value without being constantly interrupted. I usually recommend reserving capacity for urgent operational work and reviewing the portfolio regularly so strategic items don’t get pushed aside by every short-term request. At the same time, I make sure long-term priorities are visible in leadership discussions and linked to business outcomes, not just technology goals. If all we do is react to current pressure, the organization never moves forward. If we ignore operational needs, trust breaks down quickly. The balance comes from having clear prioritization rules, honest capacity planning, and regular review cycles so both types of demand are managed intentionally.
