Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Upcoming SlideShare
What to Upload to SlideShare
What to Upload to SlideShare
Loading in …3
1 of 21

From idea to concept - webinar by Michał Krochecki



Download to read offline

This presentation will help you make your first steps when creating an application. You will be able to painlessly prepare a brief that could be used in multiple situations. Most importantly, you will be better organized and have a clear path towards the final goal.

The presentation was used to conduct a webinar - follow our facebook page to be informed about upcoming webinars.

Related Books

Free with a 30 day trial from Scribd

See all

From idea to concept - webinar by Michał Krochecki

  2. 2. WHO WE ARE VISUALITY ▸ Since 2007 ▸ 100 + apps ▸ Agile ▸ Business driven development ▸ Full-stack ▸ Ruby on Rails/React.js
  3. 3. INTRODUCTION IDEA VS CONCEPT ▸ Idea as a mental construct is an impression that we have, an inkling about something that we would like to do. ▸ A concept is the final form of the idea, that prior to it’s appearance, needs polishing, documenting, setting goals, start points and end points. ▸ When ideas are often abstract, unstructured, chaotic and emotional, concepts are far more precise and tend to be lacking in emotions.
  4. 4. INTRODUCTION IDEA VS CONCEPT ▸ When our clients come to us they often mistake an idea for business with the actual business plan. ▸ Almost every time, the final concept is different. Why? ▸ Technological barrier. ▸ Complexity. ▸ Timeframe . ▸ Budget.
  5. 5. CASE STUDY 1 LEARNING PLATFORM ▸ Client wanted to revamp the current training system for accountants. ▸ New UX/UI planned. ▸ Completely new type of user = new target. ▸ Effect? ▸ Completely new product emerged. ▸ It was separated from the old platform.
  6. 6. CASE STUDY 2 TRAINING PLATFORM FOR CAR MECHANICS ▸ Initial idea: ▸ Client wanted to create a database with questions and instruction videos for beginner mechanics. ▸ Each question was linear and non-related to other. ▸ Videos were mainly about precise and difficult tasks like changing clutch. ▸ Pay as you go only.
  7. 7. CASE STUDY 2 TRAINING PLATFORM FOR CAR MECHANICS ▸ Concept emerged after the workshops: ▸ Gamification model (rewards, badges). ▸ Specific cases to solve with multiple related questions, you needed to play as diagnostician. ▸ Videos as extra content. ▸ Pay as you go & subscription model.
  8. 8. VERIFYING THE IDEA ASK YOURSELF THESE QUESTIONS ▸ Why do I want to do this? ▸ What kind of problem do I want to solve? ▸ Do potential clients know that they have this
 problem? ▸ Do I know how to solve this problem? ▸ What benefits will I offer? ▸ What resources/budget do I have? ▸ What do I want to achieve (number of users, subscriptions bought etc.) ▸ Do I want to fund the project on my own or do I seek investors?
  9. 9. VERIFYING THE IDEA WILL SOMEBODY USE IT? ▸ If there is no such product on the market does it mean that nobody needs it? See Sony’s Walkman case. ▸ Call your friends and family and ask them what they think. ▸ If your product is related to your current professional area, ask your coworkers and even your superiors. Who knows, maybe your current working place will be your first client. ▸ Ask experts like business advisors, people who invested in startups or people like us.
  10. 10. RESEARCHING THE MARKET COMPETITION ▸ Start with search on Google: ▸ Prepare keywords that would describe your business and use them in search. ▸ Research Google trends. ▸ Set Google Alerts for the keywords to see if some new players arrived and to track your competitors activity. ▸ Go to SpyFu, Alexa, Compete etc. and check the stats about your main on- line competitors (paid option). ▸ Why not calling them? You don’t have to lie, you can just say that you are interested in their company :)
  11. 11. RESEARCHING THE MARKET COMPETITION ▸ Social media and content marketing (remember that not every sector is active on social media): ▸ Check what kind of content your competitors publish. ▸ See what they lack. Do they appear as experts? ▸ Follow them on Facebook and Twitter. ▸ Sign up for their newsletters/blogs. ▸ Test competitive products (if it’s possible), note down everything that could be done better.
  12. 12. WRITING A GOOD BRIEF IN NUTSHELL GENERAL INFO ▸ Make it simple, easy to read for technical and non-technical people. ▸ Make two separate lists of elements, before you write a brief: must have and good to have. ▸ Always remember about your budget. ▸ If you need comparisons visit Crunchbase and see how much funding startups receive to get the idea.
  13. 13. WRITING A GOOD BRIEF IN NUTSHELL BUSINESS PART ▸ What do you want to sell? Is it know-how? Is it a service? Is it a downloadable product? ▸ What is the problem and the solution you want to offer? ▸ Name and describe your competitors (what and how they do it, how they advertise, how many clients they have etc.). ▸ Why are you/will you be better then your rivals? ▸ Who is your target client? Create a profile of a typical client. ▸ Describe a client’s journey (Client Journey Mapping).
  14. 14. WRITING A GOOD BRIEF IN NUTSHELL TECHNICAL PART ▸ Do you need a web app, mobile app or both? ▸ How secure the app should be? Will you store sensitive data? ▸ Does the target market have any legal/technical barriers like VOIP blocking in UAE? ▸ Do you require connection to Google Analytics? ▸ If you do, what project management method you’d like to choose: agile, waterfall etc.
  15. 15. WRITING A GOOD BRIEF IN A NUTSHELL TECHNICAL PART ▸ Functions: ▸ Login/Sign up (how many steps?) ▸ Languages/time-zones ▸ Modular build ▸ 3rd party software integrations ▸ Payments/subscription model/currency ▸ Search functions ▸ Tagging/labeling ▸ Booking system/schedules ▸ Notifications ▸ Chat/messaging in app ▸ OCR solutions ▸ Data import/export
  17. 17. WORKING WITH PARTNERS WHAT SOFTWARE HOUSES DO? ▸ Feasibility study ▸ MVP/Product workshops ▸ Estimation (different techniques) ▸ Backlog creation/refinement ▸ Development ▸ UX/UI design
  18. 18. WORKING WITH PARTNERS MVP/PRODUCT WORKSHOPS ▸ An industry standard. ▸ Last from 2 to 5 days. ▸ Brain storming about the ideas. ▸ Shaping the ideas into a concept. ▸ Defining user flows, system elements, integrations etc. ▸ Discussing the UX/UI.
  19. 19. WORKING WITH PARTNERS MVP/PRODUCT WORKSHOPS ▸ Product definition. ▸ The outcome = full documentation and mockups. ▸ Easy way to design hi-fidelity mockups or final designs. ▸ Easier to pitch to an investor or potential clients. ▸ Possible precise estimation of the product.
  20. 20. MAKING THE DREAM COME TRUE PIECE OF ADVICE ▸ According to lean startup method you can often start a business offline in order to test the idea in practice, be able to iterate and pivot, if necessary, faster than usual. (Zappos, , Food on the Table - bought by Food Network) ▸ Pitch to clients investors in the meantime, don’t waste time! When the product is good it will spark interest even before it’s ready or even before you start developing it. (Dropbox). The knowledge you gain is precious! ▸ Try to measure A/B - why show everyone the same thing? ▸ Sometimes we build landing pages for our clients to allow them to make an appearance, let people know that something is coming soon. Perfect for lead generation. ▸ It’s better to show something imperfect than to show nothing. You don’t have to be a second Apple. ▸ MVP doesn’t have to be basic, but it should be as simplest as possible to complete the Build-Measure-Learn-Feedback Loop. ▸ Check - Diagram adapted from Ries, E. (2011) 'The Lean Startup,' New York: Crown Business.
  21. 21. QA QA