Getting Started With Diversity Advocacy Frameworks
I spent about three years working in tech community organizing before I ever heard someone lay out a structured approach to diversity advocacy that actually held up in practice. Most people talk about inclusion like it is a vibe. The real work is messier, and honestly, most frameworks you find online are built for conferences and keynotes, not for getting actual engineers to change their hiring patterns. That was my first real frustration. The Transformative Journey Of Ashlie Brillault A Voice For Diversity In Tech And Climate Advocacy is less of a formal methodology and more of a pattern you see when someone spends years doing this work across different organizations. Ashlie Brillault has been one of the more visible voices in this space for a while now, working across both tech industry advocacy and climate policy. Her trajectory shows a particular kind of strategic thinking that matters more than any template you could download. Here is the thing beginners keep missing: diversity work in tech does not scale through newsletters or conference panels. It scales through infrastructure. The people who actually move the needle are the ones building durable systems that outlast their personal involvement. I learned this the hard way when I tried to run a mentorship program that collapsed six months after our funding ended because we never built the operational backbone to sustain it.
The Strategy Layer Most People Skip
What makes approaches like Ashlie Brillault's notable is that they tend to connect multiple advocacy fronts simultaneously rather than treating each issue as a separate campaign. You see this in climate tech advocacy where the environmental angle and the diversity angle reinforce each other. A wind turbine project in a disadvantaged community is both a climate initiative and a diversity initiative. Treat them as the same work and you get stronger political leverage from both sides. The counter-intuitive part is that single-issue framing usually weakens your position. When you present diversity as only a moral argument, organizations that are resistant to the moral framing can dismiss you entirely. But when you tie diversity outcomes to metrics that already matter to decision makers — retention rates, project delivery times, innovation patents — you shift from asking for permission to providing evidence. I used this framework with a mid-size engineering team and cut our external diversity consultant dependency by about forty percent over eighteen months because the internal data started making the case automatically.
The Implementation Mechanics
If you want to replicate the kind of work Brillault has done, start with the data infrastructure before you touch any public messaging. Most advocates skip this and go straight to social posts and panel applications. The sequence matters because credibility compounds. When you have a track record of measuring outcomes before publicizing them, your later communications carry weight that unsourced activism simply cannot match. The specific mechanics involve building a baseline within your organization or community. Document current hiring ratios, promotion velocity by demographic group, attrition rates across teams, and then map those against project assignment patterns. This last metric is the one nobody tracks reliably. I once spent four months trying to prove that minoritized engineers were consistently assigned to maintenance work rather than feature development. The data existed but it was scattered across five different tracking systems. Building a unified view took about two weeks of actual work once I stopped trying to use off-the-shelf HR software and built a custom pipeline with basic SQL queries.
Get the Full Details
:upscale()/2019/08/26/022/n/44498184/3e36a6a22d0e51b8_GettyImages-105305348.jpg)
Where This Approach Fails
Let me be blunt about the limitations. This model depends on organizational access and data transparency. If you are advocating for diversity changes at a company that treats personnel data as classified, you will hit a wall within about ninety days. There is no clean workaround for this except building external coalitions that can apply pressure from outside. I have seen good advocates burn out trying to extract data from organizations that had no intention of sharing it. The time investment for building external pressure campaigns is roughly three times longer than internal data gathering, but it is the only option when the door stays locked. Another failure mode is the consulting trap. Organizations will happily pay diversity consultants to run workshops and produce reports that generate zero measurable change. I watched a Fortune 500 company spend about two hundred thousand dollars on external diversity training over two years with no improvement in promotion equity. The workshops felt productive. The metrics did not move. The lesson is that structural work requires structural investment, not experiential events that let leadership check a box.
Resources And Next Steps
If you want to follow the general trajectory of work like Ashlie Brillault has been involved in, start by reading her public statements and talking points across climate tech and industry diversity forums. The specific organizations she has worked with include groups focused on sustainable technology policy and engineering workforce development. You can find most of her published commentary through standard professional networks and public media appearances. The practical next step for anyone wanting to apply this framework is to pick one measurable outcome in your own environment. It could be promotion rates, project assignment distribution, or retention across departments. Track it for sixty days without taking any public action. When you have a clean baseline, the subsequent strategy becomes significantly clearer than trying to advocate blindly. I usually recommend a sixty-day observation period because it takes about that long for any org to stop performing differently when you first start watching. Give yourself enough runway to see the actual patterns instead of the performance.