StoryCareer Editorial
Published Aug 3, 2026 · 1 min read
My first product was a two-person build with an eight-week deadline. I learned that writing the spec was the easy part — the hard part was saying no.
I moved into product after four years in customer support, where I had heard every frustration our users had. When I got the chance to own my first feature, I was determined to fix everything at once.
The roadmap I drafted would have taken four months, and I had eight weeks. Every stakeholder had a feature they considered essential, and I kept adding scope until the delivery date had no room for testing or fixes.
I sat down with engineering and we cut the scope to a single core flow: users could solve the one problem they contacted support about most often. I wrote a one-page spec, showed it to ten customers for feedback, and we shipped on time.
Mornings are for user interviews and reading support tickets. Afternoons are split between writing acceptance criteria, clarifying requirements with engineers, and keeping the team focused on the current milestone.
Your job is not to build more features, it is to make sure the team builds the right one. Learn to say no kindly, and validate assumptions with users early — a week of interviews beats a month of guessing.
After eight years in corporate jobs, I left to build a small software product. It failed twice before I found something people were willing to pay for.
I started a weekly newsletter about marketing experiments. Two years later it pays a meaningful part of my income — and it taught me more than any job.
I moved from a retail job into security analysis through free labs, homelab practice, and a first role that paid less than my old job but taught me everything.