Skip to content

Q&ACIO-261117

How IT Leaders Build Shared Priorities Across the Business

CIO Grid

When every department calls its request urgent, IT leaders need a clear way to set shared priorities. This article features insights from experienced IT and business experts on weighing impact, cost, risk, and delivery time. These practical methods help teams make fairer decisions and focus resources on what matters most.

§ How this was made

The perspectives in this article were written by the named contributors and submitted through Connectively. Connectively's automated system selected them and used AI to write the headline, introduction, section headings, summary sections, and illustration, and to make minor edits for clarity. Articles are assembled and published automatically. Report errors to corrections@connectively.us. How we make our content

Illustration generated with AI

What the experts said

25 on console

  1. Require Backers to Identify SacrificesJason Hennessey
  2. Rank Demands by Downtime ToleranceJens Hagel
  3. Publish Cost of Delay RankingsNick Kuang
  4. User Removed This ResponseDeleted User Deleted User
  5. Grant Each Team a Monthly Emergency SlotSahil Agrawal
  6. Compare Impact Against Delivery TimeNicolas Falourd
  7. Center Choices on User PainJordan Vickery
  8. Weigh Shared Criteria Against ConstraintsHasan Can Soygök
  9. Record Assumptions in Decision ReceiptsBrian Hansen
  10. Cap Unplanned Capacity With Preemption BudgetsSherif Koussa
  11. Expose Consequences Through Visible LedgersChirag Kulkarni
  12. Separate Emergencies From Long-Term ValueDane Maxwell
  13. Limit Workflow ExceptionsDawood Bukhari
  14. Distinguish Essential Operations From EnhancementsJames Rowell
  15. Let Business Owners Choose OutcomesEvgeny Leonov
  16. Assign Deferral Risks to SponsorsChrissy Grigor
  17. Route Scope Changes Through GovernanceScott Stouffer
  18. Demand Verifiable Urgency EvidenceNina Alexander
  19. Set Financial Authority LimitsLuba Inz
  20. Protect Reliability Before Broad ReachVishnuvardhan Reddy Kaithapuram
  21. Force Departments to Select Their Top ItemMuhammad Ahmad Khan
  22. Measure Baselines Before EvaluationDaniel Goh
  23. Require Accountable Adoption LeadsXavier Berkness
  24. Centralize Tasks on a Single BoardDanielle Lemons
  25. Judge Initiatives by Organizational BenefitAkshay Mathur

Require Backers to Identify Sacrifices

Priority conflict becomes destructive when teams bring requests but hide consumed capacity. Every initiative has second-order costs, interrupted specialists, delayed maintenance, fragmented data, and leaders making decisions with information. The queue looks crowded because those costs rarely appear on a request.

I frame the tradeoff as an exchange, not an approval. Every new commitment requires its sponsor to name what should slow down, stop, or be protected. This prevents capacity from being invented by borrowing against reliability. It also exposes preferences. A department unwilling to displace anything may want visibility, not urgency. Once that distinction is clear, leaders can reserve technical attention for work that truly changes the business trajectory.

Rank Demands by Downtime Tolerance

JHJens HagelFounder & Owner, kjello

My rule is to rank every request by one question: how long can the business run without this? The senior boss of an 80-person haulage firm in Hamburg once told me everything was fine. I asked how long they could work without their dispatch software before customers walked away. That answer set the order, and patch management came first, at a fraction of the cost of new servers.

Jens Hagel, Founder & Owner, kjello (Hamburg, Germany)

Publish Cost of Delay Rankings

When every request is urgent, urgency stops being a priority signal, so I replace it with one decision rule: the request that protects revenue or a customer commitment this month goes first, and everything else gets ranked by cost of delay.

As a former Silicon Valley program manager, I saw IT queues turn into a contest over who escalated loudest. The fix was a short, recurring intake conversation where each department had to answer two questions in writing: what breaks if this waits 30 days, and what does it enable if it ships now? Requests that couldn't answer clearly dropped down the list on their own, without IT having to be the bad guy.

The other piece is transparency. Publish the ranked list where everyone can see it, so business leaders trade priorities with each other instead of lobbying IT privately.

I still run my real estate business this way: when renovation, acquisition and marketing tasks all feel urgent, the one tied to a closing date wins.

Takeaway: swap "urgent" for "cost of waiting 30 days," and make the ranked list public.

Nick Kuang, Co-founder, Home Sweet Home Offers

User Removed This Response

Deleted by user

Grant Each Team a Monthly Emergency Slot

SASahil AgrawalFounder, Head of Marketing, Qubit Capital

When every department tells you its request is urgent, give each one a single urgent slot a month and let them spend it. Our tech team is small and builds internal tools for everyone else, which means sales, HR and marketing all queue for the same few people. Everything outside the slot joins a normal queue that the tech lead orders.

The arguments moved. Department heads now argue with their own teams about which request deserves the slot, a conversation they never had when they could mark everything urgent. I sit out of most of it. A strong second request from the same team sometimes waits 4 weeks purely because of the calendar.

Compare Impact Against Delivery Time

We settled competing urgencies by forcing a single, short prioritization conversation that compares customer impact and implementation time, not opinions. At Cyber Techwear we stopped treating every request as urgent and began asking two direct questions in the meeting: who benefits (customer, revenue, ops) and how long to deliver.

Decisions go to whoever owns the metric affected (conversion, uptime, fulfillment) and the team commits to a delivery window or a rollback plan. That simple rule turned long debates into fast trade-offs and made visible the real cost of shifting scope mid-sprint.

Center Choices on User Pain

JVJordan VickeryCo-Founder, Vinyl

I think one of the biggest problems with competing priorities is that every team naturally sees its own requests as urgent. The most useful way to move the conversation forward is to stop discussing which department needs something most and start asking which problem has the greatest impact on customers. I'd look at how often the issue occurs, how much friction it creates, and what happens if it isn't addressed.

We learned something similar while building Vinyl. Our initial focus was on online meetings, but repeated feedback from accounting firms showed us that important client conversations were also happening face-to-face. That helped us recognize mobile recording as an important addition rather than just another feature request. The lesson for me is that a shared understanding of the customer problem makes prioritization much easier. Teams may disagree about solutions, but it's harder to disagree about the importance of solving a problem that customers repeatedly experience.

Weigh Shared Criteria Against Constraints

My decision rule is that every new urgent request must identify which existing priority it would displace. I ask business teams to explain the customer impact and cost of delaying their request, while IT assesses technical risk, dependencies and implementation effort. Security and compliance issues receive particular attention because their consequences can extend beyond individual departments. We then compare requests against shared criteria rather than allowing the most vocal team to determine priorities. I document the agreed trade-offs, decision owners and timelines in Asana so everyone understands what moves forward and what must wait. This has helped turn competing demands into constructive discussions about business outcomes. Shared priorities become easier to establish when departments recognise that resources are limited and every decision carries an opportunity cost.

Record Assumptions in Decision Receipts

I use a "decision receipt" after resolving competing requests. It is a brief record of what was prioritized, what moved back, the evidence considered, and the date the decision will be reassessed. The receipt turns a potentially frustrating conversation into an accountable agreement.

Its most valuable feature is the explicit assumption. For instance, a request may be deferred because customer impact is expected to remain stable for four weeks. If that assumption changes, the priority can change without reopening the entire debate. This gives departments a practical way to challenge decisions through new evidence rather than escalation. Over time, the receipts reveal patterns, including recurring bottlenecks and teams that routinely classify ordinary work as urgent. Better priorities emerge not from perfect forecasting, but from making decisions visible, testable, and revisable.

Cap Unplanned Capacity With Preemption Budgets

Prioritization fails when the scoring model treats all impact as immediate. Some work produces value on delivery, while other work preserves the ability to deliver safely later. Unpatched authorization flaws, brittle integrations, and missing evidence for a regulated customer may not generate applause, yet delay can narrow options and inflate cost. A shared priority model needs to measure option loss, not only upside.

I recommend a preemption budget. Each quarter, leaders reserve a defined portion of engineering capacity for genuinely unplanned work, then require any demand beyond that budget to displace a named commitment. This stops every new request from masquerading as an emergency. It makes risk financially visible, including customer confidence and accountability.

Expose Consequences Through Visible Ledgers

CKChirag KulkarniFounder & CEO, Taco

We create a visible tradeoff ledger to keep shared priorities clear. Every urgent request must be matched with the work it will delay. This makes urgency more accountable because we cannot add new tasks without recognizing what must move. Leaders can still escalate important requests, but they must clearly decide what gets pushed out of the current cycle.

The goal is not to build a perfect ranking system but to make the cost of each decision clear. Teams can agree on priorities more easily when they understand the consequences of changing them. We consider whether an urgent sales request is worth delaying a reliability improvement or security commitment. Shared priorities grow when everyone takes responsibility for tradeoffs instead of expecting IT to absorb every exception.

Separate Emergencies From Long-Term Value

We create shared priorities by ranking requests against customer impact in one public list, with one rule: a request moves up only if someone can name the customers it affects. Every department can argue its request is urgent. Fewer can point to the brokerages waiting on it, and that question cuts most arguments short. The rule works because the customer base gives us a common scale. With 1,700+ active brokerages, a request that unblocks compliance reviews for many offices beats a request that makes one internal report prettier, however loudly the second one is pushed. Sales, support and engineering all talk to the same customers, so they can check each other's claims instead of trading opinions. The conversation that made this constructive was separating urgent from important in our weekly planning. Urgent means a customer cannot do their work today, and those items jump the list with no debate. Important means it will help more customers over time, and those compete on impact. Most cross-team tension came from important requests being presented as urgent ones. Once the two had their own lanes, people stopped inflating the language, because a real emergency would get handled anyway. The list is visible to the whole company, including why each item sits where it does. When someone disagrees with a ranking, they can see the reasoning and argue with that rather than lobbying whoever seems to have influence that week.

Limit Workflow Exceptions

One overlooked source of conflict is that business teams see delayed outcomes, while IT sees accumulated exceptions. Both are describing urgency, but in different currencies. Bringing those currencies into one review made decisions more constructive. Requests were evaluated for immediate impact alongside the operational burden they introduced, including manual workarounds, fragile integrations, and additional approval paths.

I advocate an exception budget. A request bypassing standard workflow must identify an exception to retire, or explain why added complexity is worth carrying for a defined period. This stops temporary fixes becoming permanent operating models. It encourages repeatable solutions across accounts, teams, and regions, rather than a bespoke answer for every urgent situation.

Distinguish Essential Operations From Enhancements

JRJames RowellChief Technology Officer, Capture Expense

Shared priorities come from agreeing on the question before arguing about the answers. When every department brings an urgent request, the conversation I find most useful is asking each team what happens to customers, or to the business, if their request waits a month. Some requests survive that question easily. Many turn out to be important but not urgent.

The decision rule that helps is separating work that keeps something running from work that improves it. Anything that stops customers from submitting or approving expenses is handled first, with no debate. Improvements then compete on value, and the business teams rank them together with technology in the same room, so the trade-offs are visible to everyone. That shared ranking matters more than the method. People accept a decision that goes against them far more readily when they watched it being made and understood the reasoning.

Let Business Owners Choose Outcomes

I get IT and business priorities into one conversation by asking what outcome each urgent request protects and what delivery constraint comes with it. Two departments may both have a deadline, but those dates alone won't tell the team what should move first. At project kickoff, our written plan captures the product's business value, feature priorities, success criteria, milestones and risks. The project manager confirms the client's priorities and success criteria, while the tech lead checks the plan's feasibility. We can then discuss a conflict in terms of what the work must achieve and what engineering can deliver.

When two requests can't both fit, I ask the business owner which outcome should survive. The technical lead explains the dependency or delivery risk of that choice. We record the chosen priority and its owner, and use the same conversation when the next change request arrives. IT can describe the cost of a tradeoff, but the business owner chooses the outcome. An urgent addition also needs an answer about what leaves the current scope to make room.

On a tutoring platform, our analyst and the client prioritized features during discovery around the core value: matching students with suitable tutors for personalized lessons. Students describing their needs, administrators assigning tutors and tutors managing lessons made up the first version. The other features went into later versions. In an organization with rival departmental requests, engineering should expose the constraint while the business owner makes the priority choice.

Reopen that decision with its owner when a new urgent request arrives. A backlog can record the result, but it can't decide the business tradeoff on the owner's behalf.

Assign Deferral Risks to Sponsors

CGChrissy GrigorPersonal Injury Lawyer & Founder, Grigor Law Injury & Car Accident Lawyers

Urgent requests often gain priority because people fear being blamed for saying no. That is a poor substitute for a decision framework. In mediation, pressure is real, but preparation changes its effect. I rely on the record, the realistic alternatives, and the consequences of proceeding without needed information.

A constructive rule is to require every sponsor to name deferral and approval consequences, including who absorbs each risk. This prevents IT from becoming default owner of business risk and prevents leaders from assuming a delay is harmless. When both sides must describe the downside in plain language, requests become comparable. The discussion becomes a choice about risk the organization will carry.

Route Scope Changes Through Governance

SSScott StoufferCo-Founder + CTO, Market Brew

My first question is whether a request changes the work we already agreed to deliver or adds a different piece of work. Urgency alone does not answer that.

At Market Brew, I use a concrete rule for changes that arrive during QA. If the specification changes the existing request, the item goes back through specification approval before continuing. If it is a new specification, it needs a separate change request and QA item. It should not quietly alter the existing request.

That gives the business requester and engineering team a useful conversation: what exactly changed, who needs to accept it, and which item owns the result? It also preserves a clear acceptance decision for work already underway. A newly urgent idea cannot become an invisible condition attached to someone else's nearly finished work.

I would make that distinction before debating priority. Once the work is explicit, people can decide what should move first and what would have to move back. A shared queue is much easier to reason about when everyone is discussing the same scope.

Demand Verifiable Urgency Evidence

A useful decision rule is that no request gets ranked as urgent until its owner has said what evidence would let it wait. When colleagues of mine are firmly on opposite sides, I begin by asking each one what they would have to see before changing their view, and the same question can be put to whole departments. Put to IT and business teams together, it asks for things that can be checked, such as how many people a fault stops from working or which genuine deadline a delay would put at risk. Requests can then be compared on those terms, which gives every department the same route to the top of the list. Give priority to the urgency someone can describe in checkable terms, and schedule the rest as preferences.

Set Financial Authority Limits

As a COO, at first there were decisions all the time, because I was putting out fires. Then it became about one decision a day. What changed it was decision limits per level, in dollars. The fourth level could make a mistake of up to $100, the third up to $500, and so on. I explained that everything you do can be translated into money.

My advice: sit down and write down the cost of mistakes. Write the limits for each role, for each level: below the limit, people decide and log it, above it, it goes up one level. Not some ghostly concepts. Numbers.

Protect Reliability Before Broad Reach

VRVishnuvardhan Reddy KaithapuramSoftware Development Engineer, Amazon

Shared priorities do not come from a meeting where everyone lists what they want. They come from agreeing, in advance, on how competing requests will be judged. When IT and business teams both see their own needs as urgent, the argument is usually not about effort. It is about what counts as urgent, and who gets to decide.

In my work at Amazon Advertising, that means starting with the impact on the teams that use the data and the systems. A request that unblocks a decision, fixes a data problem that affects many teams, or prevents a failure gets priority over a request that is loud but narrow. I have found that teams accept a decision more easily when the rule is clear before their own request is on the table. If the rule is made up after the argument starts, it feels like favoritism, even when it is not.

One conversation that helped was a regular, short review where requests were put side by side and judged on the same questions. What breaks if this waits? Who is affected? What is the cost of doing it now versus later? That review did not make every request a priority, and that was the point. It gave business teams a clear place to explain why their need mattered, and it gave engineering a clear place to explain what a change would actually involve. When a request had to wait, the reason was visible, and the next review gave it another chance.

I also try to be honest about trade offs in plain terms. If we take on one urgent request, another one moves. Saying that out loud, and naming what moves, makes the choice real. Teams are more willing to compromise when they can see the full picture, rather than feeling that their request was quietly dropped.

The decision rule I rely on is simple. Protect reliability and data trust first, then unblock the work that affects the most people, then take on improvements that can wait. That order does not make everyone happy every time, but it gives the organization a shared way to resolve competing demands. Over time, that shared rule matters more than any single priority call, because it lets IT and business teams argue about the work itself, not about whose urgency counts more.

Force Departments to Select Their Top Item

I'd put every request in one list that all departments can see, along with how much the team can realistically deliver in a month, because urgency claims shrink once people can see what their request would push back. Each department then names its single most important item rather than sending a list, so the conversation starts from real priorities instead of everything at once. At an online retailer, that might mean a new landing page for marketing and a fix to a shipping-label integration for operations sitting side by side, with the people asking deciding together which one waits. The conversation I'd start with is simply "if only one of these gets done this month, which should it be?", since it moves the trade-off from IT to the business, where it belongs.

Measure Baselines Before Evaluation

DGDaniel GohChief Marketing Officer, RankAISearch

1. Establish shared baseline numbers prior to debating the order in which to address issues. We use Google Search Console and Bing Webmaster Tools as well as a weekly log of changes made to the site. New marketing requests are always added to this document in relation to the existing numbers. What ends up being "urgent" typically goes down significantly when people can see the current numbers first. For example, a few weeks ago marketing asked for a new landing page by that week. Our own site audit revealed that one of our current pages weighed in at 2MB (in part due to 3 icons totaling 570KB each). Making that one page slightly better helped everyone, so we tackled that issue first.

2. No ticket is accepted without a baseline number plus a number that the requester wants to move to plus a time frame for verification after the change is released. Such changes are released one at a time and all activity is documented. I wouldn't want to go back to arguing about the order of tasks for automation as we do today (e.g., how many hours a week of someone's time will be saved by this new feature). Even though all such arguing doesn't ever completely cease, it gets shifted to arguing about the terms of the agreed-upon verification, i.e., "Here is what we'll know in 2 weeks."

Require Accountable Adoption Leads

XBXavier BerknessPresident & CTO, PERC Engage

Priority meetings fail when they end with a ranked list but no named business owner. IT can deliver a feature exactly as requested, yet the value never appears because nobody changes the process, trains employees, or measures adoption. That creates frustration on both sides, and the next request is often framed as another urgent technology problem.

Every approved initiative should have a business owner, a measurable expected change, and a check-in after implementation. The owner does not need technical expertise, but must be accountable for the operational result. I have found that this rule improves prioritization before work begins, because weak requests struggle to identify a real outcome. It also keeps IT from becoming the default owner of business change.

Centralize Tasks on a Single Board

DLDanielle LemonsVice President of Operations, DirecTech Connect

The rule that settles most of these fights: if it isn't on the one shared list, it isn't real yet.

At one point I was responsible for as many as 40 active client projects at the same time, and I learned that work slips through the gaps between systems: a request in an email, a change mentioned on a call, a note on a sticky pad. Once every request goes into one list that every department can see, "urgent" becomes something you compare in the open instead of something each team asserts on its own.

Two habits make that list work. First, every item has exactly one owner who is accountable for the next step, because "the team is handling it" usually means no one is. Second, review the whole board every week, not just the loud items. Urgent work finds you on its own. The project that quietly hasn't moved in nine days won't, and that is usually where the real risk is.

Judge Initiatives by Organizational Benefit

AMAkshay MathurGroup Product Manager, Softheon Inc.

In my experience, competing priorities between IT and business teams usually arise because each department measures success differently. Business teams focus on customer commitments, revenue, and timelines, while engineering teams focus on system reliability, technical debt, scalability, and delivery capacity.

As a Group Product Manager at Softheon, I manage products that support healthcare interoperability, enrollment, and data exchange across multiple health insurers and government programs. With different clients and internal teams requesting changes simultaneously, prioritization is a constant challenge.

One approach that worked well was moving discussions away from “whose request is more urgent?” to “what is the business impact of not doing this now?”

We introduced a more structured prioritization process where requests were evaluated against common criteria: regulatory or contractual obligations, customer impact, revenue implications, operational risk, technical dependencies, and engineering effort.

For example, when a client requested a new integration while engineering was focused on improving platform reliability, we discussed the consequences of delaying each initiative rather than allowing either team to dictate priority. This helped us distinguish genuine deadlines from preferences and identify opportunities for phased delivery.

I also encouraged engineering and business stakeholders to participate in prioritization discussions together, rather than having separate conversations that resulted in conflicting commitments.

The most useful decision rule was simple: regulatory and critical production issues take precedence, followed by initiatives with the greatest measurable business impact relative to effort and risk. When priorities conflicted, we made the trade-offs explicit and documented what would be delayed.

This approach helped reduce unproductive escalations, improve transparency, and create shared accountability for roadmap decisions. More importantly, it shifted the conversation from defending departmental priorities to making decisions based on what mattered most to the organization and its customers.