Process Before Tools: How to Scale Without Burnout (Michael Toguchi)

If you’ve ever felt like your team is running on duct tape and good intentions, you’re not alone. In this Building Better Developers interview, Michael Toguchi (Chief Strategy Officer at eResources) makes a simple point that changes how you approach growth: process before tools. Before you buy another platform, automate another workflow, or roll out a new system, you need clarity on how the work actually gets done—and who it’s meant to serve.

You can’t tool your way out of chaos. The real fix starts upstream—before the migration, before the CRM, before the next sprint. It starts with people, leadership, and making the work visible enough to improve it.

Process before tools isn’t a slogan—it’s the difference between scaling sustainably and scaling stress.

If you want, I can also tighten the second sentence to include the phrase again without sounding repetitive, but this version should clear the Yoast check immediately.

---

About Michael Toguchi

Michael Toguchi is the Chief Strategy Officer at eResources, where he helps lead a platform that manages complex workflows for scholarships, grants, admissions, and accessibility services. With 25+ years supporting universities, nonprofits, and foundations through digital transformation, Michael focuses on making systems simpler, sustainable, and human-centered—so teams can scale without burnout and spend more time on mission-driven work.

---

Process Before Tools: Why “Survival Mode” Becomes the Default

Michael describes a pattern that mission-driven organizations (and plenty of startups) fall into: survival mode. Everyone is moving fast, reacting to urgent needs, and doing what it takes to keep the wheels turning. The downside is that the process gets postponed indefinitely.

The team says things like:

• “We’ll document it later.”
• “We’ll clean it up after this deadline.”
• “We just need something that works.”

And it does work… until it doesn’t. When the organization grows, the cracks grow with it: inconsistent outcomes, tribal knowledge, bottlenecks, and the quiet creep of burnout.

---

Process Before Tools: Start Small, Make It Digestible

One of the strongest points Michael makes is that meaningful change rarely comes from a dramatic, top-down overhaul. The most sustainable improvements begin with small, digestible steps.

Instead of trying to “fix everything,” identify a single pain point the team feels every week:

• A handoff that always breaks
• A recurring rework loop
• A reporting task that eats hours
• A workflow that depends on one person’s memory

Then improve that one piece, measure it, and repeat.

Sustainable change isn’t a magic wand. It’s a series of small wins that teams can actually absorb.

---

Process Before Tools: You Need Leadership Alignment (Not Just Agreement)

A lot of teams confuse “buy-in” with “approval.” Leadership might approve a new system or initiative, but that’s not the same as aligning on why it matters, what success looks like, and what tradeoffs are acceptable.

Michael emphasizes clarity:

• What problem are we solving?
• Who owns the workflow?
• What will we stop doing to make room for the change?
• How will we know it’s working?

Without alignment, the organization drifts into mixed expectations—some people expect speed, others expect compliance, others expect perfect reporting. The result is frustration on all sides.

---

Process Before Tools: Win With People, Not Platforms

Michael's most practical warning is also the simplest: don’t make it about tools.

Tools can amplify a good process, but they can’t create it. If you automate a messy workflow, you don’t get a better workflow—you get a faster mess.

The winning strategy is human-first:

• build champions inside the team
• communicate the vision in plain language
• reduce fear by making the change incremental
• keep feedback loops tight

When teams feel heard, they participate. When they participate, the workflow becomes real. And once the workflow is real, the tool decision becomes obvious.

Tools don’t transform organizations—people do.

---

Process Before Tools: A Practical Takeaway You Can Use This Week

Here’s a simple way to apply Part 1 immediately:

1. Pick one workflow everyone complains about.

2. Write down the steps as they happen today (no judgment).

3. Identify one “failure point” (handoff, duplicate entry, unclear ownership).

4. Fix only that this week.

5. Tell the team what changed and why.

That’s how you move from survival mode to sustainable growth—without waiting for a budget cycle or a platform replacement.

---

Closing Thoughts

This interview is a reminder that building better systems is really about building better teams. Before you chase the next tool, tighten the workflow. Before you automate, clarify. Before you scale, align.

In Part 2, we’ll go deeper into workflow transparency, tool sprawl, measurable efficiency, and what happens when AI compresses time and challenges the way we price work.

---

Stay Connected: Join the Developreneur Community

We invite you to join our community and share your coding journey with us. Whether you’re a seasoned developer or just starting, there’s always room to learn and grow together. Contact us at [e-mail] with your questions, feedback, or suggestions for future episodes. Together, let’s continue exploring the exciting world of software development.

---

Additional Resources

• Individuals and Interactions Over Processes And Tools
• The Science Of Processes – Interview With Samuel Drauschak
• Automating Your Processes
• Building Better Foundations Podcast Videos – With Bonus Content