Every Vaditu Haseji session follows a consistent structure — but the content is entirely specific to the situation it addresses.
The structure is designed to move from understanding to action — quickly. Sessions run for half a day. You spend the morning learning and the afternoon practicing.
We open by mapping the specific type of situation the session covers. What does a peer request actually look like? What are the different forms it takes? Who's involved? What are the stakes? Participants share examples from their own experience. This grounds everything that follows in reality rather than theory.
Before you can respond to a request, you need to decide how to respond. The decision framework is a short set of questions — usually four or five — that help you evaluate the situation quickly. Is this mine to take on? What happens if I say yes? What are the real consequences of saying no? We walk through the framework with real examples until it feels natural to use.
This is the core of the session. We introduce a set of base scripts — different ways of declining or redirecting that fit the situation. Then each participant adapts them to their own voice and their own work context. You don't leave with someone else's words. You leave with language that sounds like you.
The final part of each session is structured practice. In pairs and small groups, participants run through real scenarios — one person plays the person making the request, the other practices responding. The facilitator circulates and gives feedback. This is where the learning becomes physical, not just intellectual.
The colleague who asks you to "just take a look" at something. The teammate who needs help finishing their deliverable. The person who assumes you're available because you always have been.
Peer requests feel low-stakes because the power dynamic is roughly equal. But that equality is also what makes them hard. You can't cite a hierarchy. You can't point to a formal process. You're navigating a personal relationship and a professional one at the same time.
This session focuses on how to decline peer requests in a way that's honest without being harsh, clear without being cold. You'll work through the specific language that keeps the door open for the relationship while closing it on the request.
The manager who adds to your plate without asking about your current load. The executive who has an idea they want executed by next week. The senior person who treats your time as a default resource.
Pushing back on leadership is one of the most common professional fears. The worry is real: say the wrong thing and you're seen as difficult, uncommitted, or not a team player. So most people don't push back at all.
This session is about how to have that conversation without triggering those perceptions. The key is in how you frame the pushback — not as a refusal, but as a resource conversation. You're not saying you won't do it. You're asking for help deciding what to deprioritize to make room for it.
The client who emails with "one small addition." The project that was defined in week one and looks nothing like that by week eight. The expectation that keeps shifting without anyone acknowledging it.
Scope creep is the slow erosion of an agreement. It usually doesn't happen in one dramatic moment — it happens through small additions, reasonable-seeming requests, and the gradual normalization of doing more than was agreed. By the time you notice it, you're already significantly over scope.
This session focuses on the specific skills of holding a scope conversation with a client — how to name the expansion without making them feel accused, how to present the implications clearly, and how to offer a path forward that works for both sides.
Get in touch to find out about upcoming public sessions in Atlanta or how to arrange a workshop for your organization.