top of page

From idea to implementation: 4 steps to your own product

Do you have an idea for an app, store or website? Great! Now you probably want to implement it as soon as possible, and you're looking for someone who can help you. But first, take a deep breath – it won't happen overnight. In this guide, you'll learn what will happen to your idea when you trust IT specialists to make it a reality.


We implement your idea step by step. Time to get started!


Let's start with what may seem like bad news but is actually very good news. When we create something new, we never work on the full, final version right away. We'll implement your project using one of two basic approaches: MVP (minimum viable product) or POC (proof of concept).


We try out ideas, look for product-market fit, and analyse whether the end result will sell. We create basic models using simple tools (WordPress, Wix, Spreadsheet, Airtable). We make prototype solutions and test them in the real world.

So, from the very beginning, we keep in mind that the solution we're creating may not be the final version. Why? 🤔 You'll find the answer by following the 4 steps below.


🔵 Step 1. I have an idea. Do you know what I mean?


Not yet, but we'll soon find out! 😉


As well as an explanation of the idea and the goal, the work requires an understanding of the needs of potential users.

It's a process that requires the involvement of at least a few people and is necessary for many reasons. First and foremost, it helps to avoid rookie mistakes such as working with ambiguous guidelines or taking senseless actions.


🔵 Step 2. Can I just send the materials to the software house?


Not exactly. It's not quite that simple! 😉


You probably have materials in various forms: descriptions, tables, drawings, mood boards, "almost ready" graphic design... Or you've written the idea down in a few bullet points that require many hours of development. This is not the right material for the job.


Why not?


Because it doesn't allow us to create a predictable, repeatable and high-quality result – and this is surely what you expect from us after looking at the portfolio.


The solution to this problem is to convert the materials into a standardized form. On this basis, we create user stories, mockups, graphics and more technical software architecture designs (e.g. entity relationship diagrams, flow diagrams and use case diagrams).


🔵 Step 3. We have the standardized materials. What happens next?


Now we start working on the prototype, i.e. the development of what we wrote about in the previous sections. This allows you to see what result you can get. The prototype is created in order to get feedback from users as soon as possible and quickly react to it.


How does it work in practice?


Together we create a deeper understanding of the aspects of the software that need to be developed. On this basis, a list of priorities is made. When creating the prototype, we take into account the most important elements.


What exactly is a prototype?


It can be various solutions that will allow us to quickly confirm whether key business assumptions are correct. For example:

  • an Airtable table and a simple frontend created using no-code tools (this is the POC approach – proof of concept),

  • a simple, flexible, easy-to-change website or e-commerce store,

  • a dynamic website design using JavaScript technology (e.g. React, Angular, VueJS). Such a system can include a CMS (e.g. Symfony, headless CMS), but it doesn't have to if the data won't change often,

  • minimum viable product (MVP), which is created with the target technology right away, but covers only the basic scope of functions.


🔵 Step 4. The prototype is ready. Do we start work on the final version of the design?


Not necessarily.


What we do next depends on the results of the previous actions, so we do everything we can to test them in the real world. This means it's time to evaluate and make changes – for example, we can test different options. We develop what we have and see which parts need to be changed.


However, the information obtained may show that it's worth going back to the drawing board. Then we use different technologies, develop the automation and/or implement stability, performance and security fixes.


As you can see, Agile methodology plays a major role in project management, so it's worth devoting a few words to it.


How do you successfully complete all the stages? The answer is Agile


The road from idea to implementation consists of just 4 steps – but it’s still winding and bumpy. Many changes and unexpected situations lie ahead of you. You may also reach conclusions that will require you to start work practically from scratch. This is exactly why being Agile is so important.


And this is the basis of how we work at 1000.software. We implement your project according to the Agile, Scrum and Extreme Programming approaches. This allows us to deliver individual elements iteratively, react quickly to changes and draw conclusions from what we've done so far. We push the project forward in small steps, and each decision is made based on detailed analyses.


From an idea to a solution that works. Double Diamond in practice


The steps that I've described probably remind some people of the Double Diamond model. They're absolutely right! 😉

For those who are unfamiliar with it, let me briefly explain. The Double Diamond model makes it possible to find working (effective) solutions through 4 phases:

  • Discover – consists in gathering information about the problem and its potential solutions.

  • Define – this is when we develop the data from the first stage, providing a clear picture of the actions that are worth taking, but also those that would be a waste of time.

  • Develop – this is where the actual work on the project begins, with the aim of solving the problems defined in the first two steps.

  • Deliver – now is the time to test what was previously developed (including by analysing the users' satisfaction with the solution developed).

The cyclical nature of project implementation is also reflected in other models, including the Deming cycle (PDCA) or the spiral model. These will be discussed on the blog later. So, let's sum up!


From idea to implementation – in a nutshell


So, let's say you want to send me a message asking for help in implementing your idea. What lies ahead of us?

  • First: the needs analysis and business analysis.

  • Second: standardization of the materials that you have.

  • Third: work on the prototype.

  • Fourth: testing the prototype and implementing the necessary changes.

And all this, of course, in the spirit of Agile.

Are you ready? If so, feel free to write to us!

bottom of page