Most teams don’t need more process.
They don’t need another tool, another dashboard, or another 87-slide deck explaining the new way of working.
What they do need – desperately – is permission.
- Permission to simplify something that’s become ridiculously overcomplicated.
- Permission to say “I don’t know” without feeling incompetent.
- Permission to stop doing work that nobody uses or values.
We hire talented adults and professionals – and yet many still hesitate, not because they can’t change, but because past environments have taught them to tread carefully around anything unfamiliar.
So let’s talk about 10 very practical, very human “permissions” that unlock better work, better focus, and better results.
1. Permission to Keep It Simple
Somewhere along the way, we started treating complexity like a badge of honor.
You can see it in the way people write requirements, tickets, or user stories: the entire history of the problem goes in the summary line, three paragraphs of context in the description, plus a Confluence novella linked at the bottom – just in case.
Here’s the truth:
If your story or requirement can’t fit (conceptually) on a 3×5 index card with a Sharpie, it’s probably doing too much.
A simple mental check:
- Card – What’s the essence of this thing? We need to be able to write it on a 3*5 index card (with a sharpie!)
- Confirmation – What does “done” look like (acceptance criteria)
- Conversation – What do we still need to talk about with the team
That’s it. That’s the work.
Teams often overcomplicate because they don’t feel they have permission to be simple. They worry simple looks lazy, or incomplete, or “not professional enough.”
Leaders can flip that script instantly by saying, “If you can’t explain it simply, we can’t deliver it reliably. You have permission to keep it simple.
2. Permission to Think Differently
One of the most powerful phrases you can say to a team is:
“You have permission to look at this differently.”
Think about something like a bug backlog that’s been growing for years. There are hundreds (or thousands) of items, many of them old enough to vote.
What if someone said:
“If a bug has been sitting untouched for 9 months and no one is screaming about it, you have permission to close it – or move it to a ‘Future Work’ holding pen. If it’s truly important, it will resurface.”
That’s permission to:
- Question the sacred cows
- Challenge “we’ve always done it this way”
- Let go of work that no longer matters
Sometimes, all that’s needed is a leader explicitly saying, “You’re in charge. You are allowed to make this call.”
3. Permission to Say “I Don’t Know”
In some environments, “I don’t know” is treated like career suicide.
But listen to scientists. They love “I don’t know” – because it’s the doorway to learning.
In product and delivery work, “I don’t know” might sound like:
- “We don’t know yet, but we’ll experiment.”
- “We can do this, but we’re sizing it bigger to account for risk.”
- “We don’t know the simplest approach yet; we’ll need to try a couple of options.”
That’s not incompetence. That’s honesty.
When leaders model “I don’t know, let’s figure it out,” they give everyone else permission to drop the performance of certainty and move into genuine discovery.
Innovation rarely comes from pretending you already have all the answers.
4. Permission to Experiment (and Not Get It Right)
Innovation isn’t a slogan. It’s a practice.
If every change has to be guaranteed-successful before it starts, your organization doesn’t have a culture of innovation – it has a culture of safety theater.
One simple pattern:
At the end of every retrospective, ask:
“What’s one small experiment we’ll run next sprint?”
Not a huge transformation. Not a 6-month project. Just one small, thoughtful experiment:
- Try a new way of refining work
- Test a different release approach
- Pilot a change in how you run Daily Scrum or standups
Then celebrate two outcomes:
- Experiments that work (great, keep them)
- Experiments that don’t (great, we just learned something)
When teams hear, “You have permission to try things – and permission not to get it perfect on the first go,” they stop playing so small.
5. Permission to Slow Down to Speed Up
Constant urgency is a liar.
It tells you there’s no time to pause, reflect, or fix root causes. It persuades you that the only option is to keep pushing the square-wheeled cart faster – never mind that someone is running behind you with round wheels.
“Slow down to speed up” is not fluffy. It’s strategic.
It might look like:
- Taking a sprint (or a chunk of one) to eliminate a recurring pain
- Addressing a chronic defect pattern instead of patching the latest incident
- Investing in automation, testing, or architecture that prevents future chaos
Teams need permission to say,
“We’re stuck in death by a thousand cuts. Let’s stop and put this problem down once and for all.”
Without that explicit permission, people just keep band-aiding the system and calling it progress.
6. Permission to Be the Expert
Scrum and similar frameworks talk about teams as peers: no titles on the team, just different accountabilities.
Reality? People still defer to the “master,” the “owner,” or the “manager.” They quietly downplay their own expertise.
Teams need to hear:
- “You’re the technical expert.”
- “You see this system every day in a way I don’t.”
- “I rely on you to tell me when something won’t work.”
That’s permission to:
- Speak up when a decision is risky
- Suggest a better way of doing something
- Push back when a request doesn’t make sense technically
When people internalize, “This is my domain. I am the expert,” the quality of decisions – and the quality of collaboration – dramatically improves.
7. Permission to Talk About What’s Not Working
Retrospectives are great, but feedback shouldn’t be locked in a once-per-sprint box.
Teams need permission to say, in the moment:
- “This process isn’t working.”
- “This meeting format isn’t helping us.”
- “This dependency is blocking us – again.”
That requires psychological safety. And psychological safety isn’t created by posters or values statements. It’s created by how leaders respond in the first 30 seconds when somebody raises a tough issue.
If the first response is defensiveness, minimization, or blame, people learn: It’s not safe to bring things up.
If the first response is, “Thank you for raising that – let’s look at it,” you’ve just given permission to the whole room.
8. Permission to Stop Doing Things That No Longer Serve the Team
Every organization is full of zombie work: reports no one reads, status decks no one uses, time-tracking games everyone resents, projects that will never meaningfully finish.
Consider this: If you stop doing this report, does anyone come looking for it?
If the answer is no for three months… you just found a candidate for the chopping block.
Teams need explicit permission to ask:
- “Who is this for?”
- “What decision does this enable?”
- “What happens if we simply stop?”
This extends to funding and planning as well. Instead of funding rigid projects and then torturing people to track time against mythical lines, what if we funded teams and pointed them at the highest-value work?
“I give you permission to stop doing work that doesn’t create value,” is one of the most liberating sentences a leader can say.
9. Permission to Decide Without Perfect Information
We live in a VUCA world: volatile, uncertain, complex, ambiguous.
Waiting for perfect information is a beautiful way to get stuck in analysis paralysis.
Teams need to know:
- It’s okay to make the best decision you can with the information you have
- It’s okay to pivot when new information arrives
- It’s more dangerous to never decide than to occasionally decide and adjust
Sometimes this is as simple as saying,
“Our decision-maker is on vacation. We still move forward. We are adults. We’re trusted professionals. Let’s make the call.”
Most of the time, no one comes back furious. They come back relieved something moved.
Permission to decide is permission to lead.
10. Permission to Say “No” (or at Least “Not Right Now”)
This one might be the hardest of all.
Many teams are people-pleasers in disguise. They say “yes” to every request, every urgent interruption, every “can you just…?” – and then wonder why quality drops and burnout skyrockets.
Sometimes “no” sounds like:
- “No, this isn’t ready yet; we don’t have enough information.”
- “No, we can’t safely add that to this sprint without dropping something else.”
- “No, I can’t take on one more thing and still deliver what I’ve already committed to.”
Sometimes it’s “not right now”:
- “We can absolutely do this next sprint; right now we’re at capacity.”
Saying no (or not yet) isn’t being difficult. It’s protecting focus, quality, and sanity.
Leaders can make this easier by saying,
“I expect you to protect your capacity. You have permission to say no when the work isn’t ready or when it will overload the team.”
So… What Permission Do You Need to Give Today?
Agility at its heart is not just events, boards, or backlogs.
It’s permission:
- Permission to inspect and adapt
- Permission to challenge the status quo
- Permission to try, learn, and try again
Here’s a simple challenge:
- Pick one permission from this list that your team clearly needs.
- Say it out loud in your next team meeting. Literally. Use the word permission.
- Back it up with behavior the next time someone takes you up on it.
Because once people truly believe they have permission to simplify, question, experiment, slow down, decide, and say no…
They stop just doing work.
They start doing their best work.