In my last post, I talked about the moment I realized what I had been doing was marketing tactics, not a go-to-market strategy. This post is the follow-through on that.

A go-to-market strategy, at its most fundamental, is not just about finding your ideal clients and showing up where they are. It is about increasing the likelihood that they will actually buy from you. That distinction matters more than most people realize.

The fact is, people do not buy from people they do not know. They buy even less from people they do not trust. A real strategy is designed to close that gap: to demonstrate your value consistently, before someone ever reaches out. Not by talking about yourself constantly, but by showing, through the work you share and the way you show up, that you are exactly who you say you are.

For me, that trust is built on one thing above everything else: knowing operations.


What I Look At

When I come into an engagement, I am not making assumptions. I am asking questions, observing systems, and mapping what is actually happening versus what leadership believes is happening. Those two things are often very different.

Here is the diagnostic lens I bring to every organization I work with:

Time and Resources
  • Where is time being drained?
  • Where is money being drained?
  • Are the right people doing the right work, or is high-cost talent stuck doing low-value tasks?
Systems and Tools
  • Are there bottlenecks that can be removed?
  • Is there an opportunity to introduce an AI tool or automation to reduce manual work?
  • Are the tools currently in place actually being used as intended, or has the team built workarounds around them?
Structure and Accountability
  • Is there a clear chain of command, or are decisions stalling because no one is sure who owns them?
  • Is accountability distributed appropriately, or is everything funneling to one person?
  • Is the same responsibility being handed to too many people, or are too few people carrying too much?
Knowledge and Continuity
  • Does critical institutional knowledge live in a single person's head? If that person left tomorrow, what would fall apart?
  • Are there standardized processes and procedures in place, or does each team member do things their own way?
  • Do the SOPs in place actually align with organizational policies, or have they drifted?
Communication and Handoffs
  • Are there breakdowns in communication between departments?
  • Where do things fall through the cracks when work moves from one team to another?
  • Do staff have a clear, trusted channel to surface issues to leadership?
Visibility and Tracking
  • Does leadership have real-time visibility into what is actually happening on the ground?
  • How are results, errors, and progress being tracked?
  • Are decisions being made with data, or on instinct?
Scalability
  • Can the current systems and structures handle growth, or will they break under pressure?
  • Is the organization prepared for what comes next, or just surviving what is happening now?

Where I Start

I look at the full picture, from senior leadership all the way to frontline staff. In practice, I prefer to start at the frontline. Those are the people living inside the friction every single day. They will tell you exactly where things are breaking, why, and how long it has been that way. Working my way up from there gives me a much more honest picture than starting at the top and working down.

Some consultants prefer the reverse, and that is a valid approach. My preference is to be thorough. I want to understand every layer of what is impacting the organization, how, and why, before I make a single recommendation.


Who This Is For

Operational dysfunction does not belong to one industry. It shows up in startups and established firms, in nonprofits and corporations, in lean teams of five and sprawling organizations of five hundred. The symptoms look different on the surface, but the root causes are remarkably consistent: unclear ownership, unmapped processes, communication gaps, and systems that were built for a version of the organization that no longer exists.

If your team is working hard but the results are not matching the effort, there is usually a structural reason for that. That is exactly where I come in.

My background includes launching and scaling programs at both the state and federal levels, work that earned me the 2024 Director's Award from the Department of Justice. Creating structure where there is none, and building systems that can carry an organization forward, is the gift I bring to every engagement.

Start at the Beginning
What I Thought I Knew
← Read Part One

Frequently Asked Questions

What does an operations consultant actually do?

An operations consultant assesses how an organization functions internally — identifying where time and money are being drained, where accountability is unclear, where knowledge is siloed, and where systems are breaking down. They map what is actually happening versus what leadership believes is happening, then build the infrastructure to close that gap. The goal is not to issue a report. It is to create lasting structural change.

How do you identify operational dysfunction in an organization?

Operational dysfunction usually shows up as a gap between effort and results: teams working hard without matching output, decisions stalling without clear ownership, institutional knowledge trapped in one person's head, and workarounds that have become unofficial standard procedure. A thorough diagnostic covers seven areas: time and resources, systems and tools, structure and accountability, knowledge and continuity, communication and handoffs, visibility and tracking, and scalability.

Why start a consulting engagement with frontline staff instead of leadership?

Frontline staff are living inside the friction every single day. They know exactly where things are breaking, why, and how long it has been that way. Starting at the frontline and working up gives a more honest and complete picture of what is actually happening, as opposed to what leadership believes is happening. Those two things are often very different — and that gap is usually where the dysfunction lives.

What is a knowledge silo and why does it matter?

A knowledge silo occurs when critical institutional knowledge lives in a single person's head rather than being documented and distributed across the organization. If that person leaves, is unavailable, or is overloaded, the organization loses access to the information it needs to function. Knowledge silos are one of the most common and most underestimated risk factors in operational continuity.

How do you know if your organization needs an operations consultant?

If your team is working hard but results are not matching the effort, there is usually a structural reason. Common signs include: decisions stalling without clear ownership, the same problems recurring without resolution, new staff struggling to get up to speed because nothing is documented, communication breaking down between departments, and leadership lacking real-time visibility into what is happening on the ground. Any of these signals is worth a conversation.


Gladian Rivera is the Founder and CEO of Obsidian Rising LLC and a strategic operations consultant with 20+ years of experience navigating complex institutional environments across justice, healthcare, and nonprofits. She is a 2024 Director's Award recipient from the Department of Justice, a fourth-degree black belt, a bilingual speaker, and the author of The Sovereign Leader. Connect with her at obsidianrisingllc.com, follow her on Facebook and Instagram @obsidianrisingllc, or connect on LinkedIn.

If Any of This Sounds Familiar, Let's Talk.

Whether it is the bottlenecks, the knowledge silos, the accountability gaps, or simply the sense that something is off but you cannot name it — that is a conversation worth having. I review every submission personally and will follow up within 48 hours if there is a potential fit.

Start the Conversation