This is a bridge, not a pivot.
For a while, I have known this blog needed to evolve.
Not because my past work no longer fits, but because the context around that work has changed.
When I first started this blog, I wrote mostly about project management, digital transformation, citizen development, accessibility, data privacy, and the different ways technology could be used for good. At the time, that framing made sense.
It reflected the work I was doing, the clients I was supporting, and the questions I kept seeing across startups, nonprofits, and other mission-driven spaces.
And all of that still matters.
I still care about accessibility, true data privacy, internal communications, systems design, and building better workflows.
I still help people turn ideas into something useful and real.
Those parts remain unchanged.
The most significant shift is recognizing a deeper urgency to address systemic impacts in all my work.
Over time, it became harder to discuss technology, communication, or operations as if they existed in a vacuum.
The systems we build affect real people.
At the end of the day, the systems we build affect real people, and the words organizations use affect us as well. Not only do words impact trust and, quite literally, reality, but the tools we choose to use can directly affect safety, access, and dignity (this is one of the reasons I no longer support this company). And when OUR rights are under pressure, even basic operational decisions (like capitulating on ending DEI programs at universities) start carrying more weight.
Of course, that is only part of why my blog is evolving.
Where clarity comes from
Some of this clarity came from my work building statewide multilingual, ADA-accessible, and HIPAA-compliant telehealth systems, as well as from projects where communication shaped whether people could actually access care. I have also supported community-facing tools, public resources, and cross-sector collaboration as a Know Your Rights Trainer. More recently, I have been helping build movement infrastructure and rapid-response communications to support people protecting fundamental rights (The Firewall Network) and working on other initiatives (COPAL, 3 Waters PRT, Minnesota DFL, and more). Something even more relevant is that in mid-2025, my husband and I moved to Minneapolis and served as constitutional observers and organizers as Operation Metro Surge unfolded.
When you work closely with systems and actually get involved, you start to see the pattern. And that pattern is getting clearer.
It is where clarity originates.
And the focus must shift.
The issues I am talking about are rarely just about a particular tool (literally and figuratively). You cannot codify action in the sense of democracy. Instead, it’s the structure around it.
It is the language around it.
It is the governance around it. I wrote more about that question in who gets a say before those decisions harden into structure.
It is who gets protected, who gets ignored, and who is expected to absorb the risk. I wrote more about that question in practice in who carries the burden when systems fail.
That is why I do not think of my work as “just tech” or “just MarCom.”
And I do not think of this blog as a place for abstract commentary. I am more hands-on than that.
I build infrastructure, and sometimes that means workflows. Other times, it could mean content systems or accessibility reviews, governance decisions, or stronger communication plans. A majority of the time, though, it means helping people make sense of a system that was never designed with them in mind.
What matters and what’s next?
To me, that is where applied management still matters.
I did not study applied management to better understand business (P.S., there’s a difference between what I do with Applied Management and it is not business management).
Instead, my goal was to bridge real-world complexity with practical action, because what I had previously experienced in corporate America was more fragmented than cohesive or impactful. It was empty. I was empty, and I wanted a way to connect analysis with implementation. I wanted something that could hold strategy, operations, communication, and change simultaneously. I needed something that showed me how what I was doing was positively impacting something bigger than myself, versus being solely focused on putting out fires that could easily be prevented.
That lens still guides me.
It just now lives in a sharper context.
I am less interested in helping organizations sound “innovative.” Instead, I am more interested in whether their structures actually help people.
I am also interested in whether/how a tool, process, or message ACTUALLY impacts someone, and how we can DEMONSTRABLY protect dignity, improve access, and ultimately reduce harm.
Why this blog is evolving.
It is not becoming a personal journal. It is not becoming a policy blog. And it is not becoming a stream of hot takes.
This is still a blog about systems, communication, technology, and implementation.
Moving forward.
I will be writing about them with more honesty about the stakes, how my past and current experience connect the dots, and how that impacts you directly. And what you can do about it.
What to expect.
That means you can expect more writing about rights, public health, accessibility, data ethics, movement infrastructure, and how ordinary people can contribute from their own role, sector, or skill set, and how it all connects back to ALL of OUR fundamental rights. It also means I will be writing more plainly about authoritarian creep, because I do not think complexity should be used to keep people passive. It’s quite the opposite.
What not to expect.
At the same time, I am not interested in empty performance.
I do not think everyone has to call themselves an activist.
I do not believe everyone has to start with ideology.
And I don’t think shouting louder always helps (it rarely does).
Where you, my readers, come in.
What I do think is this: People can make a difference from where they already are.
If you’re a healthcare worker, you can protect patient dignity.
Throughout various fields, a project manager can improve the structure of a campaign.
Different kinds of technologists can reduce risk and/or increase access.
A communications specialist can help make complexity easier to understand.
An educator or teacher can help others connect the dots.
Volunteers can help information travel farther (than fear).
That is the kind of work I want this blog to support. That is also why I wrote How to Defend Rights From Where You Are, which focuses on how people can contribute from the roles and skills they already have.
So yes, this blog is changing, but this is not a hard pivot. It’s a bridge.
Building the bridge(s), not wall(s).
This is ultimately why my blog is evolving. It will serve as a bridge between the work I have already done and the work I want to make more visible. A bridge between technology and rights. Between systems and people. Between strategy and action. Between professional skill sets and the bigger public stakes surrounding them.
If you have been reading for a while, thank you for staying with me.
If you are new here, welcome.
Either way, as we move forward, the goal is to be more direct, more grounded, and more honest about what I believe technology, communication, and systems work should actually be for: Usefulness, clarity, and access.
And structures that help people hold the line.