Don’t Just Follow — Explore, Fail, and Build Your Own Way
I’ve been thinking about something lately, something I wish every fellow tester, every new tester, every curious learner could hear.
Here it is:
There is no fixed path.
No one-size-fits-all.
No perfect roadmap.
Not in testing.
Not in life.
Not in how we grow.
Most people expect their career to be like Maps. Start at point A, follow some “expert-approved” path, and reach point B: success. But that’s not how it works.
Not in our field.
Not in the real world.
🧭 The Journey Isn’t Linear, and That’s Okay
When you start your testing career, it’s natural to feel lost. You want a mentor. You crave direction. You might even feel frustrated because no one’s guiding you properly.
But here’s the truth:
You’re not walking a straight road. You’re exploring a wild landscape.
And your mind, your growth, they don’t move in a straight line either.
So, explore.
Don’t just follow a plan. Explore everything: the UI, the APIs, the tools, the risks, the ideas behind the product. Try boldly. Discover what’s broken. Learn fast.
Try. Fail. Learn.
You’ll slowly find your rhythm, your voice, your unique way of testing.
At first, it feels slow and messy. But later, you’ll look back and realize:
That “mess” built the tester in you.
There’s no GPS/Map here.
You need to build your own compass, and that comes from curiosity, critical thinking, and exploration.
Example: Testing by Thinking and Questioning
In the early days of my career, I was working at a startup and helping a friend build an image editing platform from scratch. I wore many hats, gathering requirements, coordinating with developers, and aligning with stakeholders. It was a raw and evolving environment: requirements lived in Google Docs, bugs were tracked in spreadsheets, and tasks moved through Trello. No formal structure, no defined processes, but we all shared a vision.
When it came to testing, we didn’t have tools, frameworks, or even test cases. But we had something more important: critical thinking and a deep understanding of our users.
So I asked:
What if a user uploads a damaged image?
What if they undo multiple steps rapidly?
What happens if they save before an edit finishes applying?
and more …..
I approached testing not as a checklist, but as an exploration. I imagined real-world scenarios, stressed the system intentionally, and questioned everything the user might do, especially the unexpected.
That experience taught me something fundamental:
Good testing doesn’t start with tools—it starts with questions.
🔀 Two Kinds of Growth Paths
Not everyone gets the same kind of learning environment, and that’s okay. But you have to play your hand right.
1. If you’re in a place where you can explore:
You’re lucky. Use that freedom to think critically. Test beyond assignments. Ask deeper questions. Don’t wait to be told what to test. Try things. Question everything. Uncover what’s broken. Make your own testing map…
2. If You’re in a Strict, Structured Org:
And if you don’t get room to experiment, follow someone who is worth following.
Find a tester who’s doing it right. Walk their path for a while. Learn from their habits/knowledge/skills.
But remember: when you finally get the space, don’t just keep copying.
Start building your own way.
Following someone will make you good.
But exploring on your own — that’s how you become the best.
💥 The Power of Intention
Some people are given opportunities to explore — but they waste them.
They get distracted. They scroll endlessly. They avoid discomfort.
Others? They get just one small window… and they create something incredible.
What’s the difference?
Intention.
When your intention is clear and honest, when you truly want to grow, you will.
But growth isn't just about willpower. It's also about direction.
Here are a couple of powerful heuristics to help you think more clearly and navigate uncertainty:
1. SFDIPOT (also called San Francisco Dipot)
This is a simple way to explore and understand a product deeply and quickly.
It stands for:
Structure - What is it made of?
Function - What does it do?
Data - What kind of data does it use or produce?
Interfaces - How does it connect with users or other systems?
Platform - Where does it run (hardware, OS, browser)?
Operations - How is it used or maintained?
Time - What happens over time (delays, schedules, time-based behavior)?
I use this as a guide when I start exploring a new feature or system.
Learn more: Sharon breakdown of SFDIPOT
2. FEW HICCUPPs
This is a checklist I use while testing to find hidden issues — especially the weird or unexpected ones.
It helps me notice edge cases, odd behavior, or confusing moments.
It stands for:
Formality
Explainability
World
History
Image
Compatibility
Capacity
Usability
Platform
Purpose
Structure
Each word points to an area where problems often hide.
It’s a great tool for spotting subtle bugs during hands-on, exploratory testing.
More details here: FEW HICCUPPs by Michael Bolton
Remember:
Heuristics don’t replace thinking—they support it.
They support you when you’re navigating complexity and ambiguity.
Start with intention.
Then explore with clarity.
Want to go deeper?
Check out more heuristics here:
👉 Mind the Gap – Ministry of Testing
Final Words
You might look at someone experienced and think,
“Maybe if I just follow their path, I’ll reach where they are.”
And yes — that might get you to a good place.
But if you get the chance to explore on your own?
You might go even further than they ever did.
So here’s my message to you:
Explore deeply. Follow wisely. And build boldly.
Testing isn’t about formulas. It’s about finding your way through complexity.
Let your curiosity lead. Let your intent stay clean.
And trust, you’ll find your way. 🌱
If you found this helpful, stay connected with Life of QA for more real-world testing experiences, tips, and lessons from the journey!