What You Need to Know Before Trying to Replicate This Kind of Work
I spent about three years working in media advocacy alongside people who treated technology strategy like it was its own discipline rather than something you bolt onto the side of a communications team. Shanna Evans Architect Of Innovation In Media And Technology Advocacy is not a course you buy, a software package you install, or a certification that shows up on LinkedIn. It is a way of structuring how someone approaches the intersection of content distribution, platform policy, and technological adoption. The people who do this well rarely talk about it as a framework. They just do it. The core of this kind of work comes down to one practical thing: understanding when a platform change matters more than the content you are pushing through it. Most teams I worked with got this backward. They optimized for the algorithm before they understood what the algorithm was actually optimizing for. Shanna Evans figured this out early, which is why her approach to media and technology advocacy looks different from the usual press release machine. Here is what the actual workflow looks like when you strip away the conference keynotes and panel discussions.
The Practical Workflow
Step one is mapping the policy surface area. Every major platform has terms of service, community guidelines, algorithmic ranking signals, and partnership programs. These are not the same thing. They overlap, they contradict each other, and they change without public notice. The first practical move is documenting what you can see today and treating it as a living file. I kept a shared spreadsheet at my old office with columns for platform, policy type, last updated date, and impact level on our content. It took about twenty minutes a week to maintain and saved us from publishing things that got silently deprioritized on two separate occasions. Step two is identifying the levers you actually control. This is where most advocates lose time. You can control your posting schedule, your content format choices, your engagement patterns, and which platforms you invest in. You cannot control the underlying recommendation engine, you cannot control shadow banning without evidence, and you cannot control how a platform decides to monetize or demonetize a topic. I have seen teams waste six months trying to reverse engineer algorithm updates by testing variables one at a time. That rarely works because the algorithms are multivariate and intentionally opaque. The workaround I used was to pick three controllable levers and run them consistently for thirty days before changing anything else. Consistency beats cleverness in this space. Step three is building the distribution network before you need it. This sounds obvious until you are in a situation where a story breaks and your only distribution channels are whatever algorithm happens to be favoring that day. I learned this the hard way during a project where we had strong editorial content but no email list and minimal cross-platform followings. When the piece finally got traction, it peaked in about forty-eight hours and then died because there was no owned audience to carry it forward. After that, every project required a minimum viable audience built before launch. Usually that meant a simple newsletter and a couple of active social accounts with real engagement history. Not vanity metrics. Actual replies, actual shares, actual return visitors.
Common Mistakes I See People Make
The first mistake is treating advocacy as if it is the same as awareness. Getting views is easy. Getting the right people to act on what they saw is much harder. Shanna Evans has talked about this distinction in interviews, and it shows up in the actual work. A campaign that gets a million impressions but zero downstream action is not advocacy. It is advertising without a conversion path. The second mistake is ignoring platform dependency risk. If your entire advocacy strategy lives on one platform and that platform changes its policies, you lose everything overnight. I have watched organizations go from having a significant voice to near invisibility because a single algorithm update shifted their reach by seventy percent. Diversification is not about being everywhere. It is about having at least three independent channels where your audience can find you if one disappears. The third mistake is underestimating how much documentation matters. When you are advocating for something, the people who need to cite your work are busy. If you are not producing clear, well-sourced, easily referenceable materials, your advocacy stays in the realm of opinion. I once had a partner organization try to use our research in a policy brief and they could not find a single data point because our reports were written in blog format with no raw numbers or source links. We rewrote the reporting template after that and added a standards section to every publication.
Get the Full Details
What This Approach Actually Looks Like in Practice
Let me walk through a specific scenario. Say you are working on a media literacy initiative and you want to influence platform policy around how misinformation is flagged. The wrong approach is to write a passionate thread and hope it reaches the right person. The practical approach is to first study the existing policy document line by line, identify the specific clause you want to change, gather evidence that the current clause creates measurable harm, and then present that evidence in the format that platform's policy team already uses for internal reviews. I tried pushing policy feedback through public channels once and it went nowhere. The exact problem was that the platform's trust and safety team receives thousands of public suggestions weekly and has a triage process that filters anything without structured data. My workaround was to find an academic partner who could package the same argument as a peer-reviewed case study and submit it through their research liaison program. That piece actually got cited in an internal policy memo six months later. It is slower than a viral tweet. It lasts longer.
Limitations and Where This Fails
This approach does not work when speed matters more than precision. If you are responding to a breaking news event or a rapidly evolving crisis, the methodical documentation and evidence-gathering process will make you late. In those situations you need a different playbook that prioritizes rapid response over long-term policy influence. I keep a separate fast-track protocol for exactly those moments, and it involves simplified messaging templates and pre-approved talking points rather than original research. Another limitation is that this kind of work requires access to people who are already inside the systems you want to change. If you are an external advocate with no professional connections at the relevant platforms or organizations, the pathway from observation to influence is much longer and less predictable. Networking in this space is not about collecting contacts. It is about becoming someone others find useful enough to share information with informally. That takes time and it takes consistency.
What You Should Actually Do First
Pick one platform. Study its current policy documents. Write down three specific ways those policies affect the work you are trying to do. Then decide whether your goal is to change the policy, work around it, or build an audience that is not dependent on it. Each of those paths requires a different set of skills and a different timeline. Most people skip straight to trying to change the policy because it feels the most impactful, but it is also the hardest path and the one with the lowest probability of near-term results. The people who sustain this kind of work over years tend to be the ones who accept that progress is slow and cumulative. They treat each policy review cycle, each platform update, and each audience growth metric as a data point rather than a win or loss. That is a lot closer to what Shanna Evans Architect Of Innovation In Media And Technology Advocacy actually involves than any keynote speech will tell you.
