01
Product Strategy
Turning fuzzy business goals into a clear, prioritized roadmap — with the tradeoffs made explicit and the riskiest bets tested first.
Product strategist · Dhaka, Bangladesh
Welcome to my little corner of the internet.
Hi there, I’m Tahsin.
I help businesses understand what customers truly need, find the right opportunity, and build products that make a meaningful difference.
I enjoy learning how different industries work and choosing the right technology—whether that’s AI, automation, analytics, mobile, or web—to solve the problem. Technology is a means to an end, not the end itself.
Currently exploring how teams turn AI experiments into useful, responsible products.
AI & automationCross-functional leadershipProduct strategyCustomer discovery
How I Can Help
Four ways I move products
forward.
Whatever stage you’re at, the work starts with understanding the problem
— then choosing the smallest thing that moves the needle.
02
Customer Discovery
Getting close to real users through interviews and data, so we build what people actually need instead of what we assume.
03
AI & Automation
Finding where AI and automation create genuine leverage, then building responsibly — measuring impact, not hype.
04
Cross-Functional Leadership
Aligning design, engineering, and business around one outcome, keeping teams unblocked and moving with momentum.
My Philosophy
Technology should never come first.
Every market has its own customers, constraints, workflows, and economics. The first job is to understand how those pieces fit—and where they break.
Only then can we choose the right way to solve the problem. Sometimes that means AI. Other times it means automation, analytics, mobile, web, IoT, or a simpler operational change.
AI is a powerful part of my toolbox, but it is not the destination. A useful product starts with a clear problem and ends with an outcome people can see.
The process
Listen. Learn. Build.
A simple loop I keep coming back to — the discipline is in running it honestly, again and again.
Listen Step 01
Get close to the people experiencing the problem. Interviews, data, and a lot of honest questions before any solution is on the table.
Learn Step 02
Turn signals into a sharp point of view. Frame the opportunity, size the bets, and decide what is worth building first.
Build Step 03
Ship the simplest useful version, measure the real outcome, and iterate. Kill what doesn’t work without ego.
A Journey of Learning
Learning Through Different Markets
My career has never been about changing jobs. It’s been about learning new industries.
Every industry has its own language, workflows, regulations, customers, and ways of measuring success. Throughout my career, I’ve deliberately embraced opportunities to step into unfamiliar domains, learn how they operate, and build products that solve problems unique to those businesses.
Those experiences continue to shape how I approach product strategy today. Rather than specializing in a single industry, I’ve learned to quickly understand new markets, identify customer needs, and choose the right technology—whether that’s AI, automation, analytics, mobile, or web—to create meaningful solutions.
Roadmap of growth
Each chapter is a new context, a new problem, and a new level of responsibility.
My career began in infrastructure, networking, systems administration, and technical support. Those years taught me what happens behind the interface: how software is deployed, how servers and networks keep it available, and how systems are maintained when real people depend on them.
That technical foundation still shapes how I work with engineering teams today. I can think about the customer-facing experience while understanding the systems underneath it, communicate across product and engineering, and make decisions with a practical sense of how technology will be operated over time.
Perspective gained Good product judgment grows stronger when it understands how technology is built and operated.
This was the chapter where I discovered how much I enjoy entering an unfamiliar business. I encountered healthcare interpretation, international development, manufacturing, regulatory intelligence, tax, compliance, and enterprise software—each with its own vocabulary and definition of success.
Hospitals needed dependable scheduling and communication. NGOs needed data that could explain real-world impact. Manufacturing teams needed precision across engineering workflows and bills of material. Tax professionals needed to follow changing regulation across markets. Moving between these worlds taught me how to listen before prescribing a solution and how to find the operating logic beneath a complex domain.
Perspective gained Domain expertise begins with curiosity, careful listening, and respect for how the business already works.
Maya introduced me to one of the most human-centered product domains: digital healthcare. The platform supported deeply personal needs around women’s health, pregnancy, mental health, and access to care. People were not simply completing tasks; they were often seeking help at vulnerable moments.
Building in healthcare required every decision to balance empathy, privacy, engagement, accessibility, and medical responsibility. Work across Bangladesh, Pakistan, and Sri Lanka also showed me how healthcare systems, cultural expectations, partnerships, and reasons for trusting a product differ from one market to another.
This chapter reinforced that technology alone cannot solve a healthcare problem. The experience around the technology must make people feel safe, understood, and confident enough to take the next step.
Perspective gained In high-trust markets, empathy and responsibility are product capabilities.
This chapter was about designing AI for everyday people. Instead of asking someone to learn another application, we explored how a familiar phone call could become the interface. People in Bangladesh could speak naturally with an AI assistant, making voice the product rather than an added feature.
That experience showed me that model quality is only one part of a successful AI product. Local language, accessibility, speech behavior, trust, and the rhythms of a natural conversation all shape whether someone is willing and able to use it. A technically correct response can still feel completely wrong for the person hearing it.
I learned to design around human behavior rather than around the novelty of the technology. That perspective continues to influence how I think about consumer AI and interfaces that need to disappear into everyday life.
Perspective gained Accessibility begins when products speak the language of their users—literally and culturally.
Maritime logistics introduced me to one of the world's most operationally complex industries. Behind every shipment is a network of vessels, navigation intelligence, logistics data, people, ports, and decisions spanning organizations and time zones. The software has to remain dependable inside an operation that never really stops.
Although my role centered on customer operations, my deepest learning came from seeing what happens after enterprise software is implemented. Adoption depends on much more than features. Onboarding, documentation, operational analytics, responsive support, and long-term customer relationships determine whether a product becomes part of the daily operation.
Working remotely from Bangladesh with customers and colleagues across North America and Europe also taught me how clarity and trust are built asynchronously. Good documentation and thoughtful communication were not administrative work; they were part of the product experience.
Perspective gained A product must fit the operation, not ask the operation to fit the product.
Moving into enterprise AI meant learning how to build products in a space where the technology, customer expectations, and business models were all evolving at once. I worked across AI SaaS platforms, document intelligence, prompt management, workflow automation, enterprise knowledge systems, and agentic AI—often taking ideas from early discovery toward a product that a business could understand, adopt, and pay for.
The challenge was separating technological capability from actual business problems. A model might be remarkable and still not solve something anyone is willing to pay for or restructure their operations around. Product thinking meant staying focused on the customer's decision-making instead of the novelty of the technology.
This chapter reinforced that AI is not a destination but a tool in a much larger problem. The discipline remains the same: understand the market, listen to customers, and build something that meaningfully changes their work.
Perspective gained AI is a capability. The product is solving a business problem that matters.
The Thread Between Them
Looking back, every chapter added another layer to how I think about products. Infrastructure taught me how technology works beneath the surface. Healthcare taught me about trust. Logistics taught me about operational continuity. AI taught me to separate an exciting capability from a meaningful business problem.
The constant has never been one technology or one industry. It has been curiosity: learning how a business works, understanding the people inside it, and building a product that fits their workflows and realities.