BOUND Framework

Key benefits

• Uses objective evidence instead of opinions to ground discussions in reality
• Uncovers the real business drivers behind unrealistic requests
• Creates collaborative solutions that stakeholders help develop and own
• Documents agreements to prevent future scope creep and misunderstandings

Questions Reflacto asks

Reflacto turns the method into these concrete reflection questions:

1. 1B - Baseline: What is the realistic situation based on facts, constraints, and what I know right now?
2. 2O - Objectivity: What evidence or reasoning can I use to ground this discussion in reality rather than assumptions?
3. 3U - Understand: What underlying needs, concerns, or pressures might be shaping this stakeholder's expectations?
4. 4N - Negotiate: How can I frame balanced options or trade-offs that lead to a constructive decision?
5. 5D - Document: How will I capture and share what we've agreed on so it stays clear and aligned over time?

Common questions about resetting expectations

How do I push back on a deadline I can't meet?

Raise it early with evidence, not late with an apology. The order that works: establish where things actually stand, take the other side's need seriously, offer two or three options across scope, timing and resources, then put the outcome in writing. Raising it days before the deadline removes every option the other side had.

How do I say no at work without damaging the relationship?

Don't say no to the request — say no to the combination of scope, deadline and capacity. "That's not possible" ends a conversation; "in four weeks we can do A completely or B in outline — which helps you more?" continues it. The difference isn't diplomacy, it's that you're handing them a choice.

What if the expectation comes from senior leadership?

Then it isn't a feasibility question, it's a prioritisation question. The thing to ask isn't "can we do this?" but "what does it displace?". Bring the list of what falls off and let the decision happen where it belongs. That's not refusal — it's the information leadership needs and usually doesn't have.

Why is documenting part of the method?

Because differently remembered agreements are the most common way this unravels. A good conversation feels settled, and three weeks later each side is holding a different version. A short written summary — what was agreed, what's open, who decides by when — takes five minutes and prevents the next escalation.

Origin and Reflacto's adaptation

BOUND has no external origin — it is Reflacto’s own mnemonic, assembled from established practice rather than adapted from one named method. The sources below document the underlying practices it draws on, such as negotiating a shared baseline and understanding where an expectation came from, not the name BOUND itself.

What Reflacto changed

Each letter maps to a distinct move: Baseline and Objectivity ground the conversation in facts rather than assumptions, Understand asks what need sits behind the stakeholder’s expectation, Negotiate frames trade-offs, and Document captures what was agreed so it stays clear later.

Primary sources and further reading

• Association for Project Management: compromise in stakeholder engagementThe British chartered body for project management on negotiating a shared baseline across conflicting expectations.
• Lange: expectation management in projectsdeA Springer Vieweg volume on how expectations arise in projects and how to work with them.

Related reflection methods

Compare another method that approaches a similar situation from a different angle.

• Stakeholder Alignment FrameworkAn important conversation about support, budget, or strategy is approaching.Open guide
• Interest-Based NegotiationTeams are blocking one another, pursuing competing priorities, and need a mutually workable solution.Open guide