JEP: Just Enough Process – Building a Lean QA Framework for Startups
By Igor Goldshmidt, Testing & Quality Engineering Expert
How I Turned Startup Chaos into a Repeatable System for Quality and Delivery
1. Why “Just Enough” Became My Survival Strategy
Every startup QA lead knows the moment when chaos quietly wins. Features move faster than testing, bugs live longer than releases, and “we’ll check it before the demo” becomes the official regression plan.
I’ve lived this story — more than once.
Each time, the question was the same: “How do we add process without slowing everything down?”
After trying and failing with borrowed frameworks, heavy templates, and Jira workflows copied from enterprises, I realized the answer wasn’t more process — it was better timing.
That’s how JEP — Just Enough Process — was born.
2. The Origin of JEP
When I first read “Manage Software Testing” by Peter Farrell-Vinay, one line stood out:
“Start from where you are.”
He was writing for large organizations, but that sentence perfectly describes what startups forget when they try to “get serious” about QA.
You can’t copy-paste enterprise structure into a five-person team. You need something alive — something that grows with your team instead of slowing it down.
So I started designing what I now call JEP — a Lean QA framework built directly from the field: real projects, real delivery pressure, and real late-night releases.
3. From JIT to JEP — Borrowing from Manufacturing to Build Better QA
When I looked for a name, I realized: this idea already exists — just in a different industry.
In the 1970s, Toyota changed manufacturing with JIT (Just-in-Time). Factories used to overproduce — mountains of parts “just in case.” JIT flipped that logic: deliver exactly what’s needed, exactly when it’s needed.
That mindset removed waste, improved quality, and empowered teams to focus on flow, not bureaucracy.
Most QA processes today look like pre-JIT factories:
- We stockpile test cases no one runs.
- We write massive test plans no one reads.
- We manage more templates than releases.
That’s inventory waste in testing.
So I applied the same logic to QA. JEP — Just Enough Process — is software’s version of JIT. It means:
- Deliver the right process step at the right moment.
- Keep documentation minimal and actionable.
- Eliminate delays between code, test, and release.
- Focus on flow, feedback, and visibility — not ceremony.
3.1 The JIT → JEP Mapping
JIT didn’t mean no process — it meant a smart, perfectly timed process. JEP applies that same rhythm to testing: run the right checks, at the right depth, at the right time.
4. What JEP Looks Like in Practice
When I join a startup as QA Lead — usually one senior (me) and a few juniors across Frontend, Backend, and Infrastructure squads — I start with one question:
“What’s the smallest process we can define that prevents repeating the same mistakes?”
Then I built around that answer.
This is the QA version that survives startup speed — lightweight, data-driven, and maintainable.
5. The “Embedded + Lead” Model
Farrell-Vinay described feature teams: small, cross-functional groups where testing is built into the product stream.
That’s exactly how I structure JEP.
- Each junior tester sits inside a squad — close to developers and features.
- As QA Lead, I define common processes, tools, and reporting.
- Knowledge flows sideways — QA isn’t a department; it’s a connector.
The result? Developers gain awareness of quality. Juniors grow faster. And the organization builds a testing system that scales without adding management layers.
6. Core Principles of JEP
- Minimum Viable Process — If it doesn’t improve speed and understanding, it’s waste.
- Embedded Quality — Each squad owns its testing; QA leads orchestrate and coach.
- Automate the Repetitive, Ritualize the Critical — Daily sanity runs and release gates are sacred.
- Visualize Everything — Mind maps, dashboards, Qase boards; clarity beats documentation.
- Evolve Continuously — Treat your process like code: review, refactor, iterate.
7. Lessons from the Field
When the process is too heavy, engineers resist it. When it’s too light, chaos returns.
JEP lives in the middle.
It’s a breathing framework that grows with the team. Once the team starts owning quality and metrics become self-explaining, you realize: the process hasn’t disappeared — it’s just become part of the culture.
That’s when testing stops being a phase and becomes a reflex.
8. Final Thoughts — A Compass, Not Armor
In large enterprises, process is armor — it protects the organization from itself. In startups, process must be a compass — something that helps you move fast without losing direction.
That’s what JEP is: a lean, living system that balances speed with stability, autonomy with accountability, and testing with trust.
It’s how I’ve learned to build quality teams from the ground up — one simple, well-timed process at a time.
Because great QA doesn’t come from more rules, it comes from the proper rules, applied just in time.
Call to Action
If you’re leading or building QA in a startup, try applying Just Enough Process in your next sprint. Ask yourself:
What can we remove without losing quality? What’s the smallest step that would make our testing more predictable tomorrow?
Start there. That’s your first version of JEP — and once you feel the flow, it’s hard to go back.
Full Disclosure
This article is the first version of an idea I’m testing — just like any process. I plan to keep refining JEP through real projects, experiments, and conversations with other QA leaders. If you’ve tried something similar — or have your own “lean quality” lessons — I’d love to hear from you. Because, like every good test, this framework isn’t finished until it’s proven in the field.
