When I joined PathAI, a startup in pathology, I knew almost nothing about the healthcare field. I didn’t understand a pathologist’s workflow, who used their services, or even how they fit into the medical ecosystem. But in those early weeks, I had the freedom to ask all the “dumb” questions—things like:
Why does the FDA need to approve our clinical surveys?
Why can we sell to clinical trials but not directly to pathologists?
Why doesn’t the engineering team talk to product?
The first six months are a golden window for questions like these. Nobody expects you to know everything yet, so you won’t lose face by digging deep. As time goes on, though, those same questions can come across as out of touch. Use this time wisely to fill gaps in your knowledge and uncover inefficiencies others might have overlooked.
Pro Tip: Write down all the jargon and processes you don’t understand. It’s amazing how often you’ll come back to that list later.
Record Your Beginner Experience
Before you get too comfortable, sit down with the product you’ll be working on and record yourself walking through it. Narrate everything you see and think as you:
Sign up for the app.
Test the first-time user flow.
Use the features as if you’re the target audience.
By recording this, you capture the unfiltered frustrations and confusions of a new user. Over time, you’ll adapt to the quirks of the product, and those first impressions will fade. Later, when you’re tasked with improving the user experience or tackling bugs, you can revisit your recording to see the product with fresh eyes again.
Choose Your Trail: A-Lines, B-Lines, and Trailblazing
A high-level design exec once gave me some great advice that applies to any new job: think like a mountain biker.
When you first join a company, you’re a rider, not a trail builder. You don’t have the political capital to create entirely new paths yet, so start with the “A-line”:
A-Lines: These are the main paths already in motion. Join an existing project and help it succeed. It’s the safest way to build trust and credibility early on.
As you gain momentum and earn political capital, you can start taking on B-lines:
B-Lines: Slightly riskier paths that branch off from the main trail. These might involve adding a feature adjacent to an existing one or tweaking a process.
Eventually, once you’ve established yourself, you can tackle the hardest (and most rewarding) challenge:
Trailblazing: This is about carving entirely new paths—introducing bold ideas, creating new product lines, or rethinking old systems. It’s risky but transformative.
The key takeaway? Don’t rush into trailblazing. Use your beginner status to map out the terrain first, then gradually work your way up.
Plant Flags for the Future
While you’re exploring those A-lines, keep staking out potential new trails. Use your recordings, questions, and observations to mark areas for improvement or innovation. When the time comes to pitch a bold idea, you’ll have a clear map of opportunities—and the credibility to back them up.
Final Thoughts: Be “Stupid”
Being a beginner is a unique advantage. You’re the only one in the organization seeing things for the first time, and that perspective is priceless. Embrace it. Ask the questions, record your experience, and build a foundation of trust by supporting existing initiatives.
Later, when the time is right, you’ll be ready to blaze new trails.