Request a Decision Challenge

Emergent Skills · Decision Challenge

The decision looks reasonable. Is the evidence strong enough to commit?

Before you commit the money, people, time, and operating disruption, test what has to be true.

You may already have a business case, financial analysis, implementation plan, vendor proposal, or pilot. This form gives Emergent Skills the starting information needed to examine the decision, the evidence behind it, the alternatives, and the work required to produce the expected result.

The numbers can be right and the decision can still be wrong. A projected benefit may depend on an assumption that has not been tested, work that has no clear owner, or an operating change that has not been shown to work under the conditions that matter.

Bring one consequential decision.

Brief answers are enough. Use the records you have, and say when you do not know. An unknown is more useful than a confident guess.

1

Define the decision

Tell us what you are considering, who can make the decision, what you would commit, and when the decision is due.

2

Show us the case

Tell us the expected result, the alternatives, what has to be true, and the evidence supporting or challenging the proposal.

3

Show us the work

Tell us what has to happen after the decision, who will own that work, and where you see constraints, dependencies, or disagreement.

You can also upload the business case, financial model, proposal, implementation plan, pilot results, research, or operating records being used to make the decision.

Decision Challenge Input

Start with the decision itself.

You do not need to have every answer. Missing or disputed information stays visible in the review rather than being filled in with assumptions.

State the decision as specifically as you can. For example: “Approve a $250,000 software rollout across three departments.”
Include a measure, target, or observable result if one exists.
Include money, staff time, contracts, implementation work, customer commitments, operating disruption, or other obligations that matter.
Include doing nothing for now, delaying the decision, making a smaller commitment, or using another approach when relevant.
List the important conditions you are relying on. It is fine if some are assumptions rather than established facts.
Include new work, changed work, implementation, handoffs, approvals, training, data work, transition work, ongoing support, or work that must stop.
Consider authority, skills, information, funding, available time, dependencies, handoffs, workload, suppliers, customers, or other constraints.
Examples: operating records, financial analysis, customer data, pilot results, vendor information, research, estimates, previous experience, or comparable projects.
Business case, proposal, financial model, implementation plan, pilot results, research, estimates, presentations, relevant operating records, or other supporting material.
Unlimited number of files can be uploaded to this field.
20 MB limit.
Allowed types: pdf doc docx xls xlsx csv ppt pptx txt.
Examples: budget limit, service level, customer commitment, regulatory requirement, deadline, acceptable downside, or contractual obligation.
If nobody disagrees, say so. Include the reason for the disagreement when known.