Hello {{first_name}}, you're in great company. You're joining 3,204 charity and social impact leaders reading this each week, all of us working on the same craft - telling stories that build trust, unlock funding, and make positive change visible.

Last week, after the edition on hostile comments, I asked you whether your team is carrying something unspoken. The pattern that came back is more interesting than the numbers.

What this tells us: The teams carrying something they have not yet surfaced are also the teams least likely to reply to a poll about it. This edition is for them too.

In my conversations with UK charity teams over the last twelve months, one question keeps surfacing more than any other. It is almost never asked directly. It hides inside other questions.

All of those questions are the same question.

It took me a long time to understand what was actually being asked. People are not really waiting for a verb. They are waiting for a person. They are waiting for someone with more standing than them to look at the work and say, you are allowed to talk about this now.

Here is the part that gets harder before it gets easier. That person is not coming. There is no certifying body in this sector that hands out the right to speak. There is no committee, no senior figure, no community elder who can grant it on behalf of everyone affected. The permission you are waiting for is not in your inbox. It is not coming next month either. The day you decide to stop waiting is the day the work starts to move.

For the first ten years of speaking publicly about my late fiancé Naz, about LGBTQ+ acceptance, about honour-based abuse and the rejection that costs people their lives, I kept receiving the question from every direction. From within the community Naz grew up in. From within the LGBTQ+ community I am part of. From strangers online who had never met Naz, who had never lost anyone, who decided I was either insufficient, overreaching, or both. The question landed the same way every time.

I now understand it differently. Most of the time it was not really a question. It was a tactic. The intent was to make me sit down. The intent was to make me wait for permission no one had the standing to give. The few times it was a real question, I did not yet have the answer. The reason I did not have the answer was that I was looking for the wrong thing. I was looking for someone to tell me I could speak. What I actually needed was a practice for granting permission to myself, every time I posted, on my own ground.

That distinction is the entire piece of work below.

Permission is not given. It is built. It has four parts. When all four are present, you can post. When any one is missing, you should not yet, and the failure has a name.

Ground. Do you have lived experience that puts you on the ground this post sits on, or are you standing on someone else's ground? Ground does not have to be identical to be ground. The bereaved partner of someone killed by hate has ground to speak about that hate. The carer of a person with severe mental illness has ground to speak about systemic neglect. The white antiracist organiser who has done a decade of accountable work alongside Black-led organisations has ground, with conditions. The director of a charity who has never had a sustained conversation with anyone in the community their charity serves does not yet have ground, regardless of what the strategy document says.

Relationship. If you cannot speak from your own experience, can you speak with, not for, the people the post is about? Have they had a say in whether this story is told. Have they had a say in how. If they cannot give consent because they have died, dispersed, or are in conditions where consent is not really free, are you posting with their community, or extracting from it? In the cases where direct consent is impossible, relationship is the next thing the community will look for. If the relationship is not there, the post reads as taking.

Proof. What have you actually done that earns you a place in this conversation, beyond posting in it? The platform you have built does not pay forward to the cause unless your work does. If the post is the only contribution, the permission is hollow. This is the test that catches the people whose visibility has outrun their work.

Direction of gain. Who gains from this post: the people in the story, or you? Allyship is when the gain flows to the people the story is about. Saviourism is when it flows back to you, and the work becomes a stage. Read your own draft and follow what gains. Not the actual money. The attention, the credibility, the warm feeling. Where does it land.

When one or more of these four parts is missing and you post anyway, the failure has a name. Three of them sit visibly in the sector right now.

Saviourism is what you get when direction of gain is wrong. The post is technically about a community, but structurally it is about your decision to help. The community fades into a backdrop for your moral journey. White saviourism is the specific case where this is racialised. A white narrator centres themselves in a story that belongs to people of colour, often without naming that the centring is happening. It is the most discussed case for good reason, but it is not the only case. Anyone with proximity to a vulnerable community can fall into it. Class, ability, sexuality, and citizenship all have their own saviour patterns. Direction of gain is the underlying check.

Appropriation is what you get when ground and relationship are both wrong. You take a story that does not belong to you, that you have not lived, that you have not asked for, and you tell it as if you have the standing to. The post is often factually correct. The community recognises the words. They do not recognise the storyteller. Appropriation is what happens when a sector becomes good at telling stories and bad at building the relationships that earn them.

The ally-as-saviour collapse is what you get when proof is wrong. You position yourself as an ally, and you post like one, but the visible work you have done lags behind the language. This is the hardest one because it sits adjacent to good faith. You are not extractive. You are not appropriative. You have just not yet earned the platform you are using. The post outruns the work, and the community can feel that gap even when the words look right. The fix is not better words. The fix is more work.

Last week's edition was about what to do when a hostile comment arrives. This week's question sits underneath it. If you cannot answer the permission question for your own post, you will not be able to tell, when a hostile comment lands, whether it is a stranger being abusive or a member of the community holding you to account.

Both can arrive in similar shapes. The sentence "who gave you the right to speak about this" is used by trolls and by people whose lived experience gives them standing to ask.

Your permission practice is what tells you which one is which. When the four parts are stable, hostile abuse cannot revoke them. When one part is wobbling, the comment is not an attack to be ignored. It is information. The protocol from last week handles the abuse. The framework this week handles the information.

If your storytelling is moving anything, you will be challenged. The challenge is not the cue to stop. It is the cue to check whether your permission still holds, and to keep going.

Stop looking for the person who is going to give you permission. Start writing your permission down.

The work this week is one document. Not for a single post. For the work.

Four checks. Run them before any post about a subject you do not have first-hand lived experience of. The order matters.

Check one. Ground. Do you have lived experience that puts you on the ground this post sits on? If not, what is your relationship to people who do? The fail state is: the post sits on ground you do not stand on, and you do not have a relationship that gives you any standing to speak. If this is the answer, the post is not yet ready. The fix is either a different post (about ground you do hold) or longer work (to build the relationship that earns this one).

Check two. Relationship. If the post is about identifiable people, have they had a say in whether and how it is told? If the post is about a community more broadly, are people from that community in the rooms where this work is decided? If consent from the people in the story is impossible (because they have died, dispersed, or are in conditions where consent is not free), is the relationship with their community visible in the post? The fail state is: you are speaking for people who have not asked you to.

Check three. Proof. What work, off the platform, sits behind this post? Not "I care about this." Not "I have read about this." What have you done, where the cause was the centre and you were not? The fail state is: the post is the most visible contribution you have made to this cause. Allyship that lives only in posts is the ally-as-saviour collapse.

Check four. Direction of gain. Read the post back. Where does the attention, credibility, and warm feeling land: on the people in the story, or on you? The fail state is: the story arc bends toward your decision to help, your effort, your transformation. The community is set-dressing for your moral journey. That is saviourism, whatever your identity.

If you pass all four checks, the post is ready. If you fail one, the fix is in that check. If you fail two or more, the post is not the problem. The work is.

This is a one-page document you write once for any subject you keep posting on. Update it as the work changes. Keep it where you draft your posts.

Use before publishing any post about a community or issue you do not have first-hand lived experience of.

Last week's offer generated more replies than any week of this newsletter so far. Thank you. I am still working through them. Voice notes are going out.

This week, the offer is different, because the work is different.

If you are sitting on a draft post (or a recent post) about a subject where you do not have first-hand lived experience, hit reply to this email and send me three things:

I am not going to send you a public reply. I am going to send you a short voice note, in confidence, with one observation. Whether the permission feels stable, where it might be wobbling, and which of the four checks is the priority. I am not a community member of every community I will hear about this week, and I will say so in the note. But after eleven years of getting some of this right and some of this wrong, I have learned where the wobble usually is, and I would rather you were not deciding alone.

This is not a sales conversation. It is the most useful thing I can offer this week. I can comfortably do the first three (for free) that I receive.

Charity So White - A UK collective of people of colour in the charity sector, calling out structural racism the rest of the sector has been slow to name. It’s a good starting point if you have not yet engaged with these questions in a UK charity-sector frame.

Show Your Work!, by Austin Kleon (book) A short, illustrated book on building a public practice by sharing the process of the work, not only the polished output. Kleon is not writing for the charity sector, but the principle maps cleanly onto the proof check in the framework above. If your post is the most visible contribution you have made to a cause, that is the ally-as-saviour collapse.

Neither of these is a referral. Neither earns me a commission.

If something in this edition landed for you, the most useful thing you can do is forward it to one person on your team who has been sitting on a draft they have not yet pressed publish on. Tell them you read it together. Tell them their next post does not need a permission slip from anyone outside the work.

If they want to join the list properly, they can do so here: www.impactstoryteller.org

And remember, if you have a draft you have not yet posted, hit reply this week. I read every single reply.

Until next week, sending you safe and peaceful energy.

Matt Mahmood-Ogston
Award-winning impact storyteller, photographer and charity CEO.
Portfolio: ogston.com | Follow me on LinkedIn