Sometimes the Right Product Decision Is "Not Yet"

I have a lot of product ideas. Some are good. Some need work. And occasionally, the smartest decision is to stop before an idea becomes a very expensive problem.

I was recently exploring an applicant-tracking system for public-safety agencies. On the surface, it made perfect sense.

Departments need better ways to market openings, collect applications, communicate with candidates and understand which recruitment efforts are actually working. We already had pieces that could support that process, so expanding into applicant tracking felt like a natural next step.

Then I started looking more closely at what a real applicant-tracking system would require.

Applications contain a lot of personal information. Depending on the department and position, the process may involve employment history, driving records, medical information, references, certifications, background investigations and other sensitive documents.

It was no longer just a recruiting workflow.

We would need to think through who could access each piece of information, how permissions would change during the hiring process, how long records should be retained, what needed to be deleted, what belonged to the department versus a third-party background-check provider, and what would happen if something was accidentally exposed.

Then there were audit logs, encryption, document security, consent, candidate requests, different state requirements and the possibility of storing information that our company simply did not need to possess.

My head exploded.

A Feature Can Quietly Become a Different Business

The danger was not that we could not build the screens.

We could create an application form, candidate pipeline, interview stages, automated messages and reporting. That is the visible part, the part that looks great in a product demonstration.

The real product would be everything behind those screens: privacy controls, security, compliance, retention policies, support processes and long-term responsibility for extremely sensitive data.

At that point, we would not merely be adding a useful recruiting feature. We would be moving into a different category of software with a very different risk profile.

That does not make the idea bad. It means the idea deserves more time, research and planning than I initially expected.

“Not Yet” Is Not the Same as “No”

It is easy to fall in love with an idea, especially when you can clearly see the customer need.

It is also easy to convince yourself that the difficult parts can be handled later. Build the exciting portion now, get some users and deal with the policies, edge cases and risks as they arise.

That is usually how technical debt becomes operational debt, legal risk and a support nightmare.

So I put the full applicant-tracking idea on hold.

We may still build safer pieces around recruitment: campaign tracking, inquiry forms, candidate communication, event follow-up or connections to established applicant-tracking and background-check providers. Those tools could solve meaningful problems without requiring us to store every piece of sensitive applicant information ourselves.

And perhaps, after more research and the right safeguards, we will eventually build more.

But not yet.

Product leadership is not only deciding what to build. It is understanding what you are truly committing the company to once you build it.

Sometimes “not yet” is hesitation. Sometimes it is avoidance.

And sometimes it is the most responsible product decision you can make.