Today I asked myself, What is the process of creating a product (content, project, service, physical product, anything else)?
A bit of googling, a couple of posts by others, and a lot of experience gave me this result...
discovery, cognition, and education
generation and selection of ideas: searching for and formulating hypotheses
selection of ideas: testing hypotheses
concept development and review
market and competitor research, analysis of business components
target audience study: segments - jobs - motives, barriers
test marketing
product development: engineering creation, design, content development, testing... and a bunch of other things
experiments - training - product improvement
launch of marketing strategy
management of processes
improvement of routine processes to save time, plus:
I wonder if anyone goes through all these cycles, as the theory goes. Or do they work more by intuition?
The product creation process can feel overwhelming, especially when you’re balancing different elements like ideation, validation, and the actual building phase. Here’s a breakdown of how I’ve approached it, which might resonate with you:
Ideation: Start by brainstorming ideas that solve real problems for your target market. Don’t just think about what you want to create; also consider what your potential users need. For instance, when I was conceptualizing my product, I compiled a list of recurring pain points I encountered, focusing on time-consuming content creation and ineffective scheduling.
Validation: Once you have a few ideas, validate them before investing too much time or resources. I created a simple landing page outlining my concept and collected emails to gauge interest. This step was crucial; it confirmed that I wasn’t just building something that I thought was cool, but rather something that resonated with users.
MVP Development: With validation in hand, focus on building a Minimum Viable Product (MVP). Strip away all non-essential features. For me, I prioritized end-to-end automation of content for SEO, as I found that’s what my target audience was really needing. The MVP allowed me to get something functional into users' hands quickly.
Feedback Loop: After launching the MVP, I sought out feedback. This is where you learn what works and what doesn’t. Engage with your early users and be open to criticism. You might discover that some features you thought were essential are actually not used as much as you expected.
Iteration: Use the feedback to refine your product. For instance, I realized that users struggled with content optimization and incorporated features for real-time scoring and suggestions. It’s all about evolving based on what your audience truly values.
Scaling: Once the product is stable and you have a clear understanding of your users' needs, focus on scaling. This could mean enhancing features, exploring partnerships, or expanding your marketing efforts. Benchmarking your tools against industry standards can provide insights on performance improvements.
Taking it step by step and remaining user-focused throughout the process made a big difference in my journey. Building a product is as much about listening and adapting as it is about having a solid idea to begin with. Keep it lean, stay flexible, and don't hesitate to pivot based on feedback.
This is a pretty good list, but I think most people do this process more by the seat of their pants. My own internal process is more like this:
I think it is important to note that this is not a natural thing, but is a trained thought process. You can learn to think this way (reading the right books, studies, working in very early-stage startups, etc.) and once you do you see business ideas and opportunities everywhere :)