As a child, I used to flip through a family photo album to see my relatives whom I had not seen in real life. At that time we had film cameras only, so the number of photos was not so large. Time has passed and currently, let's say, almost everyone owns a camera or a smartphone with a camera, or even both. Given that, the size of my photo album increased significantly. However, I think it's not just for me. Once my friend and I decided to recall an event we both attended. We took my photo album and tried to search there. At that time my album kept more than 30 thousand items inside. That search process looked like this Of course, we didn't find anything. Therefore, I started looking for a solution to be able to search in automatically. The solution I found was . Multimedia Data Multimedia IR systems I decided to use as Offline and as Online . digiKam Multimedia IR systems Synology Moments Multimedia IR Systems Please note, that they were selected solely based on the author's criteria, and there is no aim to advertise to anyone. Then I started using it... What I discovered in a flash is that current do not provide a flexible and automated functionality to import into . Multimedia IR systems Multimedia Data Multimedia IR systems But that wasn't the only problem. I realized that I need __ __as well. Multimedia Organizer Unfortunately, I didn't find a that could fully satisfy my needs (fixing problem metadata, working with and etc.) Multimedia Organizer digiKam Synology That's why I started creating my to cover my needs. product Honestly, I didn't expect that it would be so hard and in the meantime so interesting. Design Thinking The first product I was thinking about was "FVA Tool Set". Subsequently, another product came to my mind. As a result, a came about. Product Line "Hold on, you started from thinking of products, right?", - you will ask me. "Nope, I started from... It was ages ago and a whole is quite big. Being a developer, I started from coding". history "Was it a good idea to start from coding?", - you will ask me. "Again no. I would have started from Design Thinking if I was familiar with it." Design Thinking is a process of preparation, which consists of seven stages of creating a product: Here you need to create an artifact called "Empathy Map" with a formula - who, goal, do; Empathize-who, goal, do Here you need to create an artifact called "Empathy Map" with a formula - see, say, do, hear; Empathize-see, say, do, hear Here you need to create an artifact called "Empathy Map" with a formula - think and feel; Empathize-think and feel Here you need to describe a problem based on the "Empathy Map"; Define: Problem Statement Here you need to have a list of raw ideas to explore. There are also other stages not mentioned here. Ideate High-level product documentation Once I came up with product ideas to implement, I realized that a set of documentation artifacts to keep high-level product knowledge had to be established. Value Propositions The first artifact to consider was . which has the following components: Value Proposition for Products and Services to Customer Jobs; Mapper for Gain creators to Gains; Mapper for Pain relievers to Pains; Mapper with Value Proposition. One Pager Business Model Canvas The next artifact was . I downloaded a template and filled in the following fields: Business Model Canvas here to answer the questions: Key Partners Who are the key partners? Who are the key suppliers? to answer the questions: Key Activities What are the main tasks that the company must do well to deliver its value? to answer the questions: Key Resources What are the most important physical, financial, intellectual or human recourses the company has? to answer the questions: Value Propositions What value do we deliver to the customer? Which customer needs do we want to satisfy? to answer the questions: Customer Relationships What type of relationship does each of the customer segments expect us to establish and maintain with them? to answer the questions: Channels Which channels do our customer segments want to be reached through? How do we reach them now? to answer the questions: Customer Segments Whom are we creating value for? Who are our most important customers? to answer the questions: Revenue Streams What value are our customers willing to pay for? What do they currently pay for? How do they pay? How would they prefer to pay? to answer the questions: Cost Structure Where do the costs come from? Product Vision Board The third artifact was I downloaded a template and filled in the following fields: Product Vision Board. here to answer the questions: VISION What is your purpose for creating the product? Which positive change should it bring about? to answer the questions: TARGET GROUP Which market or market segment does the product address? Who are the target customers and users? to answer the questions: NEEDS What problem does the product solve? Which benefit does it provide? to answer the questions: PRODUCT What kind of product is it? What makes it stand out? Is it feasible to develop the product? to answer the questions: BUSINESS GOALS How is the product going to benefit the company? What are business goals? Competitive Analysis Matrix The last artifact in High-level product documentation was the I filled in the following rows for several products: Competitive Analysis Matrix with ; Vision Goal and Target segment with ; Marketing Pricing and Unique value proposition with ; End-user support Trainings, User guide and Help desk . Features Product from a user perspective As soon as high-level product documentation was ready, I decided to go deeper with more detail from the user's point of view. Persona The first artifact I created was I downloaded a template and filled in the following fields: Persona here to answer the questions: I chose a realistic and plausible picture and name. PICTURE & NAME What does the persona look like? What is his/her name? to answer the questions: I wrote in demographics, such as age, gender, occupation, and income; psychographics, including lifestyle, social class, and personality; and behavioral attributes like usage patterns, attitudes and brand loyalty. DETAILS What are the persona’s relevant characteristics and behaviors? to answer the questions: GOAL What problem does the persona want to solve or which benefit does the character seek? Why would a persona want to use or buy the product? User Journey and User Scenarios Then I tried to restore the user's way to achieving the goals. And I came up with . User Journey To show the value of the product, I created three user scenarios and posted them on YouTube. Please see the reference to watch them. Stakeholders Honestly, a bit later I realized that end users are not the only target audience for this product. And next artifact - Stakeholders - came into sight. It looks like a table with the following columns: , , , and . Table rows contain as follows: , and . Group Stakeholder Role Concerns View End users Suppliers Team members Product requirements Having defined everything from the user's point of view, I started thinking about what exactly the product will implement. Questionnaire Having no clue what is important for the user and what is not, I created a . It is a form to gather information on what , and are important. questionnaire to clarify user needs capabilities functions scenarios Capabilities Having gained an understanding of user needs, I started describing . Literally, describe key requirements. Capabilities Capabilities Features Having the capability list defined, I started preparing features. They represent significant, central functionality of the final system. I put them into the table with the following columns: , , and . The feature set helped me to create a project plan and a road map. Name Clarification Business Value Functional Requirements Last but not least step in defining product behavior was a list of , that define system detail behavior. I settled them into the table with the following columns: , , , , , and . Functional Requirements Name Architecture complexity Business Value Component Phase Feature ID Product development documents Product Road Map I believe is the most important document for a product at the development stage. I downloaded a template and filled in the following fields and rows: Product Road Map here with ; DATE Release date or timeframe with the ; NAME Name of the new release with ; GOAL The benefit a product should provide with ; FEATURES High-level features necessary to meet the goal with . Columns there are the product's different versions. METRICS Metrics to determine if the goal has been met On the top of that, it is quite convenient to keep an . online roadmap

Walkthroughs, tutorials, guides, and tips. This story will teach you how to do something new or how to do something better.

What I Learned as a Subject Matter Expert While Creating My Product

Read My Stories

Too Long; Didn't Read

Boost your HackerNoon story @ $159.99! 🚀

Why I Decided to Create a Photo Organizer and What I Learned as a Result

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

Detecting Architectural Gaps with Automation - Business Context

Create a Business Model Canvas for Your Business

Introducing The Triple Layer Business Model Canvas

Never Send a Business Model Canvas to Your Investors

The Napkin Business Canvas

Detecting Architectural Gaps with Automation - Business Context

Create a Business Model Canvas for Your Business

Introducing The Triple Layer Business Model Canvas

Never Send a Business Model Canvas to Your Investors

The Napkin Business Canvas

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps