Available for product work · Jos, Nigeria
I turn business problems into products people actually use.
IT Business Analyst and Product Engineer. I sit between stakeholders, users and engineering — finding the real problem, validating it, and shipping the solution.
Jos, Nigeria
Haruna Huyad Gashow
3
Products shipped to live users
6
Week MVP discovery-to-delivery cycles
20+
Stakeholder & user interviews run
2025
B.Sc. Computer Science, PLASU
The positioning
Most software fails for a reason nobody wants to say out loud: it solved a problem that was never confirmed. My work starts one step earlier — with the stakeholders, the users, and the evidence — so that what gets built is the thing worth building.
Discover
Stakeholder interviews, process mapping and user research that locate the real problem before anyone commits budget.
Validate
Hypotheses, prototypes and tests that make the business case explicit — and kill the ideas that don't hold.
Deliver
Requirements, design and hands-on engineering through to UAT, so intent survives all the way to production.
Selected work
Three products, three business problems
Product philosophy
Six principles that decide what I build and what I refuse to
01
Validate before building
Evidence is cheaper than code.
Every build starts with a hypothesis and the smallest test that can disprove it. Prototypes, interviews, and clickable flows retire risk before an engineering hour is spent.
02
Users first, always
The user defines the requirement.
Requirements are discovered in conversation, not invented in a document. I sit with the people doing the work until their real job-to-be-done is unmistakable.
03
Business before features
A feature without a business case is a liability.
Each scope decision maps to a commercial outcome — retention, revenue, cost, trust. If it maps to nothing, it does not enter the roadmap.
04
Data-driven decisions
Opinions open the debate; data closes it.
Qualitative research plus behavioural signal decide prioritisation. I instrument early so the next decision is better informed than the last.
05
Simplicity wins
Clarity beats completeness.
The strongest requirement set is the one with the least surface area. I cut aggressively so the core promise stays legible to the user.
06
Continuous iteration
Shipping is the beginning of learning.
Launch opens the feedback loop: UAT, usage review, interview, refine. Products earn their scope over time rather than assuming it upfront.
What others say
“I have high confidence in your skills as a software developer.”
“I'm proud of your projects, you're very qualified to be earning in dollars.”
How we could work together
A product partner who can define the problem and help deliver the answer.
Product discovery
Interviews, hypothesis testing, and synthesis that tell you whether the idea deserves a build.
Requirements & analysis
User stories, acceptance criteria, and process flows that align business and engineering on one definition of done.
Product design & delivery
Flows, prototypes, and shipped MVPs — including hands-on engineering when the team needs velocity.