Loading...
Answers
MenuWhat is the best method for presenting minimum viable products to potential customers?
Answers
Whoa, start by reading the Lean book again; you're questions suggest you are making a classical mistake made by too many entrepreneurs who live and breath Lean Startup. An MVP is not the least you can show someone to evaluate whether or not building it is a good idea; an MVP is, by it's very definition, the Minimum Viable Product - not less than that.
What is the minimum viable version of a professional collaboration network in which users create a professional profile visible to others? A website on which users can register, have a profile, and in some way collaborate with others: via QA, chat, content, etc. No?
A minimum viable product is used not to validate if something is a good idea but that you can make it work; that you can acquire users through the means you think viable, you can monetize the business, and that you can learn from the users' experience and optimize that experience by improving the MVP.
Now, that doesn't mean you just go build your MVP. I get the point of your question, but we should distinguish where you're at in the business and if you're ready for an MVP or you need to have more conversations with potential users.
Worth noting, MOST entrepreneurs are ready to go right to an MVP. It's a bit of a misleading convention to think that entrepreneurs don't have a clue about the industry in which they work and what customers want; that is to say, you shouldn't be an entrepreneur trying to create this professional collaboration network if you don't know the market, have done some homework, talked to peers and friends, have some experience, etc. and already know that people DO want such a thing. Presuming you've done that, what would you present to potential users BEFORE actually building the MVP? For what do you need nothing more than some slides?
It's not a trick question, you should show potential users slides and validate that what you intend to build is the best it can be. I call it "coffee shop testing" - build a slide of the homepage and the main screen used by registered users; sit in a coffee shop, and buy coffee for anyone who will give you 15 minutes. Show them the two slides and listen; don't explain, ONLY ask....
- For what is this a website?
- Would you sign up for it? Why?
- Would you tell your friends? Why?
- What would you pay for it?
Don't explain ANYTHING. If you have to explain something, verbally, you aren't ready to build your MVP - potential customers don't get it.
Keep working with that slide alone until you get enough people who say they will sign up and know, roughly, what people will pay. THEN build your MVP and introduce it first to friends, family, peers, etc. to get your earliest adopters.
At some point you're going to explore investors. There is no "ready" as the reaction from investors will entirely depend on who you're talking to, why, how much you need, etc.
If you want to talk to investors with only the slides as you need capital to build the MVP, your investors are going to be banks, grants, crowdfunding, incubators, and MAYBE angels (banks are investors?! of course they are, don't think that startups only get money from people with cash to give you for equity). Know that it's VERY hard to raise money at this stage; why would I invest in your idea when all you've done is validate that people probably want it - you haven't built anything. A bank will give you a loan to do that, not many investors will take the risk. Still, know not that your MVP is "ready" but that at THAT stage, you have certain sources of capital with which you could have a conversation.
When you build the MVP, those choices change. Now that you have something, don't talk to a bank, but a grant might still be viable. Certainly: angels, crowdfunding, accelerators, and maybe even VCs become interested. The extent to which they are depends on the traction you have relative to THEIR expectations - VCs are likely to want some significant adoption or revenue whereas Angels should be excited for your early adoption and validation and interested in helping you scale.
You have asked two questions. The first is what is the best method for presenting your MVP to potential customers.
A deck and a landing page is likely insufficient for an MVP so I'd suggest that you're still in the earliest stage of customer development which is design research.
The good news is that design research is all about asking the right questions. Questions around your concept might be:
What kind of collaborative efforts are you engaged in right now that require you find new and unknown collaborators?
When seeking new collaborators or looking for new collaborative work, where do you currently look?
What are the most significant problems associated with finding new collaborative work or workers with these existing sites or platforms?
On a scale to 1-10, 10 being most painful, rate the frustration you feel from the problems associated with the current state of finding new collaborative work or workers.
From there, you know what and who to optimize your product for, assuming you get enough validation from this process to proceed to build a real MVP, and that is going to need to be more than a deck and a landing page because you need to prove that people will sign-up for this AND that business can be transacted from these profiles in order to show that this is a viable business.
There have been a number of startups that have tried but died or pivoted away from the idea of a professional profile and a number that continue to struggle so I'd caution you to really do a lot of design research including ensuring you look at everything like this past and present.
To answer what will make the MVP investor-ready, it's evidence that you can inexpensively acquire people willing to complete a profile, and that there is business that can be conducted specifically because of these profiles, and specifically through your platform with some truly minimum viable number of profiles and transactions.
Happy to talk through this in a call. This is in a related space to my company so I monitor it fairly closely.
Based on your question '....best method for presenting MVP to potential customers?', I'm assuming that you are yet to attract or in the process of attracting your audience. If so, I think you may be jumping the gun here. I'd say
1. Build your audience first.
2.Engage them as you build. Ask them as you build what they want. Because your 'product' is tailored to the client and almost dependent on their engagement, you have to make it more customer-centric.
Some Questions for you to think about if you haven't already:
a. How are you attracting your clients?
b. What are they looking for?
c. What will keep them engaged on your website?
d. Would they feel comfortable referring your services to their network(s)?
e. How do you ensure that they are engaged on your website?
f. What will engage them?
g. Besides a profile, will your customer help generate content that could help expand the reach of your website, i.e. Are they consumers of content or co-providers?
h. What use is another professional profile in addition to others like Linkedin? Why yours? etc
After answering these and more questions, knowing who your clients are and finding out what they 'want', your Minimum Viable Product could then become the most attractive & tangible thing/service you can offer your clients FREE of charge. Use that to grow your audience, then gradually implement revenue generating perks or additional services worth paying for.
Feel free to give me a call to further discuss this.
Cheers,
Chike
The answer to the question begins with the definition of MVP. A minimum viable product (MVP) is a concept from Lean Start-up that stresses the impact of learning in new product development. Eric Ries defined an MVP as that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. This validated learning comes in the form of whether your customers will purchase your product. A key premise behind the idea of MVP is that you produce an actual product (which may be no more than a landing page, or a service with an appearance of automation, but which is fully manual behind the scenes) that you can offer to customers and observe their actual behaviour with the product or service. Seeing what people actually do with respect to a product is much more reliable than asking people what they would do.
The primary benefit of an MVP is you can gain understanding about your customers’ interest in your product without fully developing the product. The sooner you can find out whether your product will appeal to customers, the less effort and expense you spend on a product that will not succeed in the market.
Teams use the term MVP, but do not fully understand its intended use or meaning. Often this lack of understanding manifests in believing that an MVP is the smallest amount of functionality they can deliver, without the additional criteria of being sufficient to learn about the business viability of the product.
Teams may also confuse an MVP–which has a focus on learning–for a Minimum Marketable Feature (MMF) or Minimum Marketable Product (MMP)–which has a focus on earning. There’s not too much harm in this unless the team becomes too focused on delivering something without considering whether it is the right something that satisfies customer’s needs.
Teams stress the minimum part of MVP to the exclusion of the viable part. The product delivered is not sufficient quality to provide an accurate assessment of whether customers will use the product.
Teams deliver what they consider an MVP, and then do not do any further changes to that product, regardless of feedback they receive about it.
Proper use of an MVP means that a team may dramatically change a product that they deliver to their customers or abandon the product together based on feedback they receive from their customers. The minimum aspect of MVP encourages teams to do the least amount of work possible to useful feedback which helps them avoid working on a product that no one wants.
Now we will look at the step-by-step process of presenting your MVP to the potential customers:
1. Identify and Understand the Business Needs
At the very beginning, you should have identified a need as to why the product should exist. This could be an organizational need, or a customer need that addresses a current gap.
a) Determine the long-term goal and write it down. Answer this simple question: Why are we doing this project? A coffee shop chain, for example, may have the long-term goal of reducing time-to-checkout by 30%.
b) Identify success criteria. Next, identify the criteria that will determine whether or not the product will be successful. This will likely — and probably should — consist of more than one metric. Our coffee chain, for example, might define success by reaching that 30% time-to-checkout reduction, having 100,000 active monthly users, and reaching $1 million in monthly transactions via their app.
2. Find the Opportunities
In the first stage of planning your minimum viable product, you should have already identified market gaps or identified a problem that needs to be solved, whether for your company or for consumers. The next stage of MVP development consists of finding the opportunities to solve these problems and add value via your app.
a) Map out the user journey(s): The user journey is most easily divided into three parts: the user, user actions, and story endings.
i. Identify the user(s): These are the people who will be using your product. It’s possible that you will have more than one category of user. For example, if you have a service appointment booking app, you may have both the appointment scheduler (customer), and the service technician.
ii. Identify the story endings. For each user, there will be a story ending, which is the end goal of the user.
iii. Identify the jobs (actions). The jobs are the actions that the user or users need to take to reach the story ending and achieve the goal.
b) Create a Pain and Gain map for each action: The pain and gain map allow you to identify all user pain points and the gains the user achieves when each is addressed. This exercise lets you determine where you have the greatest potential to add value. You are then able to focus your minimum viable product on these areas while adding the less impactful ones to the product roadmap for future releases.
i) Write down the actions the user needs to complete. List the actions that you identified when mapping out the user journeys.
ii) Write down the pain points for each action. The pain points are brief summaries of the problems or inconveniences that users have when trying to complete that action.
iii) Write down the gain for each action. The gain is what value is achieved when that pain is addressed.
c) Summarize the pains and gains into opportunity statements: There are several ways to summarize pains and gains. One is to use opportunity statements that follow a “How Might We” format. For example, “How might we make it easier for users to book appointments?” This helps you translate the pains and gains you identified in the previous step into feature sentences.
3. Decide What Features to Build
In this stage, you will be able to discern what features to include in your minimum viable product, as well as the features to include on the product roadmap that are a lower priority.
a) Use opportunity statements to finalize your features. Using your opportunity statements from the previous step, finalize what features you want to build out. At this stage in the MVP development process, you will want to create feature sentences. For our Pet Adopters that are applying to adopt animals, for example, the opportunity statement “How might we expedite the application process?” could become “Reduce application processing time by 10%.”
b) Provide a breakdown of the features to include in the product roadmap. List the user and the specific opportunity statements and provide a breakdown of the features to include in the product roadmap.
c) Use a prioritization matrix (or similar method) to prioritize features. This step helps you identify where you can make the most impact on your product in relation to the urgency of the feature. Using a prioritization matrix, you can make the final decision on what absolutely needs to be included in your minimum viable product, and what features can be included in later releases. Below is our recommended format for your MVP prioritization matrix.
At this point, you should have a strong foundation to get started with developing your minimum viable product. You have identified and understand your business or customer needs; you have found the opportunities to address the pain points, and you have decided what features to build and their priority. Now, you can focus on getting your MVP to market.
Besides if you do have any questions give me a call: https://clarity.fm/joy-brotonath
When presenting a minimum viable product (MVP) to potential customers, it's essential to focus on showcasing its core functionalities and value proposition effectively. Here are some methods that can make your MVP investor-ready:
Demo Sessions: Organize interactive demo sessions where you can walk potential customers through the key features and benefits of your MVP. Allow them to experience firsthand how your product solves their pain points and adds value to their professional lives.
User Feedback Sessions: Conduct user feedback sessions to gather insights and suggestions from potential customers. This not only helps you refine your MVP based on real user input but also demonstrates your commitment to customer-centric development.
Case Studies: Present case studies or success stories illustrating how your MVP has helped other users achieve their goals or overcome challenges in their professional collaboration endeavors. Concrete examples can effectively convey the value and impact of your product.
Interactive Prototypes: Create interactive prototypes or simulations that allow potential customers to explore the functionality and usability of your MVP in a hands-on manner. This can provide a more immersive and engaging experience, helping them better understand the value proposition.
Pitch Decks and Landing Pages: Utilize well-designed pitch decks and landing pages to succinctly communicate your MVP's value proposition, target audience, and key features. These materials serve as essential tools for capturing investor interest and generating leads.
Ultimately, what makes an MVP investor-ready is its ability to demonstrate a clear understanding of market needs, a compelling value proposition, and a scalable business model. By effectively presenting your MVP through various channels and gathering feedback from potential customers, you can enhance its appeal to investors.
For further insights into building a minimum viable product, I recommend checking out this comprehensive guide: https://www.cleveroad.com/blog/how-to-build-a-minimum-viable-product/. It provides valuable tips and strategies for creating an MVP that resonates with users and investors alike.
To create a winning MVP presentation, start by clearly defining your product and its unique value proposition. Use visuals and storytelling to engage your audience and highlight key features and benefits. Be sure to include data and metrics to support your claims and demonstrate the potential success of your product.
Launch your MVP to a small group of target users early on and gather feedback promptly through surveys, interviews, or analytics. Use this feedback to iterate on your MVP, making enhancements or adjustments that align with customer needs and preferences.
When presenting minimum viable products (MVPs) to potential customers, the best way to do it is by focusing on the core benefits and value that the product provides. Keep your presentation simple and straightforward, highlighting how your MVP addresses a particular pain point or solves a specific problem for your target audience. Demonstrating how the product can make their lives easier or more efficient is key. It's important to gather feedback from potential customers during the presentation and be open to making adjustments based on their responses. Showcasing real-life examples, testimonials, or case studies can also help build credibility and trust with your audience. Overall, the key is to effectively communicate the benefits of your MVP in a way that resonates with potential customers and entices them to try it out. When presenting minimum viable products (MVPs) to potential customers, the best approach is to focus on the core benefits and value that the product provides. It is crucial to keep the presentation simple and straightforward, emphasizing how the MVP addresses a specific pain point or solves a particular problem for the target audience. Demonstrating how the product can enhance their lives or streamline their processes is essential in capturing their interest.
2. Gathering feedback from potential customers during the presentation is critical, as it allows for adjustments to be made based on their responses. Being open to incorporating suggestions and making improvements based on customer input can greatly enhance the product's appeal.
3. To further bolster credibility and trust with the audience, showcasing real-life examples, testimonials, or case studies can be highly effective. Providing evidence of the product's success and demonstrating how it has benefited others can build confidence in its capabilities.
4. Overall, the key to a successful MVP presentation is to effectively communicate the benefits of the product in a manner that resonates with potential customers. By highlighting the value proposition and showing how the MVP can meet their needs, you can entice them to give it a try and potentially become loyal customers.
Best Method for Presenting Minimum Viable Products (MVPs) to Potential Customers
Steps
1. Know Your Audience
- Research: Understand their needs and preferences.
- Segment: Group them based on relevant criteria.
2. Clear Value Proposition
- Explain Benefits: Highlight the problem your MVP solves.
- Simple Language: Use straightforward, easy-to-understand terms.
3. Compelling Pitch
- Storytelling: Share the story behind your MVP.
- Key Features: Focus on the most important aspects.
4. Use Visuals
- Demos: Provide an interactive or live demo.
- High-Quality Images: Make your presentation visually appealing.
5. Gather Feedback
- Surveys: Use structured questions.
- Discussions: Engage in open conversations for deeper insights.
6. Show Real-World Applications
- Use Cases: Provide practical examples.
- Testimonials: Share early user experiences if available.
7. Offer Incentives
- Exclusive Access: Offer special features to early adopters.
- Discounts: Provide special pricing for testers.
8. Track Engagement
- Analytics: Monitor interactions.
- Adjust: Tweak your presentation based on feedback.
Formats
1. One-on-One Meetings
- Personalized: Tailor the presentation to the individual.
- Detailed Feedback: Allows for in-depth discussion.
2. Group Demos
- Reach More: Present to multiple stakeholders.
- Diverse Insights: Encourage group feedback.
3. Webinars/Online Demos
- Broader Reach: No geographical limits.
- Recordable: Reuse the presentation later.
4. Emails
- Convenient: Send detailed info and visuals.
- Feedback Forms: Include links for feedback.
5. Landing Pages
- Focused: Dedicated page with all info.
- Call to Action: Encourage sign-ups or feedback.
Tips
- Be Responsive: Follow up and address questions.
- Iterate: Use feedback to improve your MVP.
- Build Relationships: Show customers their input is valued.
To make your Minimum Viable Product (MVP) investor-ready, especially for a professional collaboration network, you need to ensure that your presentation is compelling, clear, and demonstrates both the market need and your solution's potential. Here are some steps and key elements to include:
### 1. Refine Your Deck
Your pitch deck should be concise, visually appealing, and compelling. Here’s what it should include:
- **Problem Statement:** Clearly define the problem your professional collaboration network aims to solve.
- **Solution:** Explain how your platform addresses this problem. Highlight unique features and benefits.
- **Market Opportunity:** Provide data on the market size, target audience, and potential growth. Show there's a significant market for your solution.
- **Product Overview:** Use screenshots or short videos to showcase the MVP’s core functionalities. Make it easy for investors to visualize the product in action.
- **Business Model:** Outline how you plan to generate revenue. This could include subscription fees, premium features, advertising, etc.
- **Go-to-Market Strategy:** Explain your strategy for acquiring users and scaling your platform.
- **Traction:** Show any early signs of success, such as user growth, engagement metrics, or partnerships.
- **Competitive Analysis:** Highlight your competitive landscape and what differentiates your platform from others.
- **Team:** Introduce your team, emphasizing their expertise and relevance to the project.
- **Financial Projections:** Provide realistic financial forecasts and key metrics.
- **Ask:** Clearly state what you are asking for (funding amount) and how you plan to use the funds.
### 2. Enhance Your Landing Page
Your landing page should effectively capture the essence of your product and convert visitors into interested stakeholders or users. Key elements include:
- **Clear Value Proposition:** Clearly state what your platform does and why it’s valuable.
- **Engaging Visuals:** Use high-quality images, videos, or animations to make the page visually appealing.
- **User Testimonials:** If possible, include testimonials from early users to build credibility.
- **Call to Action:** Include strong CTAs, like signing up for a beta test, joining a waitlist, or scheduling a demo.
- **Social Proof:** Show endorsements, media coverage, or partnership logos to build trust.
### 3. Interactive Demonstration
Offer interactive demos or clickable prototypes to potential investors and customers. This allows them to experience the product firsthand and understand its value.
- **Clickable Prototypes:** Use tools like InVision or Figma to create interactive prototypes.
- **Live Demos:** Conduct live demonstrations during meetings or webinars to showcase the platform’s features and usability.
### 4. Collect and Present User Feedback
Gather feedback from early adopters and use it to demonstrate market validation.
- **Beta Testing:** Run a beta test with a group of users to gather insights and testimonials.
- **User Feedback:** Present positive feedback and case studies to show how your platform solves real problems.
### 5. Financial and Market Data
Investors need to see that there is a viable market and that your business model can generate returns.
- **Market Research:** Present data on market size, trends, and growth potential.
- **Financial Projections:** Show how you plan to scale financially, including revenue projections and key performance indicators (KPIs).
### 6. Build a Strong Online Presence
Ensure your company’s online presence is professional and informative.
- **Website:** Your website should be up-to-date and reflective of your brand.
- **Social Media:** Maintain active and engaging social media profiles to build credibility and community.
### 7. Prepare for Investor Meetings
Be ready to answer detailed questions about your MVP, market strategy, and financials.
- **Pitch Practice:** Practice your pitch to be clear, concise, and confident.
- **Q&A Preparation:** Anticipate potential questions and prepare thorough answers.
By refining your deck and landing page, offering interactive demos, collecting user feedback, presenting solid market data, building a strong online presence, and being prepared for investor meetings, you can make your MVP investor-ready and increase your chances of securing funding.
Related Questions
-
How much should I charge to develop a WordPress site?
Take the # of hours it takes you to do it and charge $50/hour. That's the price. Eventually you can charge $100/hour but that will require a bigger customer. If the customer is small < $1M in gross sales per year - charge $50/hour If the customer id medium < $1-5M / sales - charge $75 Over $5M - charge $100 The challenge you'll face is clearly defining the expectations and handoff so that you're not stuck doing stuff that you can charge for and always getting interrupted from past customers.DM
-
I have this social media idea,but no coding skills. How do I get someone to do the coding (cant afford to pay them) and not give away half of my idea?
Dilip was very kind in his response. My answer might be a bit on the "tough love" side. But that's for you to decide. My intention, just for the record, is to help you (and those like you) on your path to success. And that starts with having a viable philosophy about entrepreneurial-ism and business. And I'm going to answer this because I get asked some form / version of this question very frequently from newcomers to entrepreneurial-ism. The scenario goes something like this: "I have a great idea. It's amazing, I love it, and I just KNOW it's gonna make me a ton of money. But I have no money right now so I can't afford to (fill in the blank with things like "to build it / create it / market it / etc" or "to hire the required staff needed to work in my business to sell it / develop it / etc"). And I don't want to tell anyone about my great idea because I'm worried someone will steal it and make MY million / billion dollars. But I can't afford to legally protect it either... So how do I launch without the skills to personally create the product AND no money to hire anyone else to do that either??" The answer is ... You don't. Look - let's be honest. All you have is an idea. Big deal. Really. I'm not saying it's not a good idea. I'm not saying that if properly executed it couldn't make you a million / billion dollars... But an idea is NOT a business. Nor is it an asset. Until you do some (very important) initial work - like creating a business model, doing customer development, creating a MVP, etc - all you really have is a dream. Right now your choices are: 1. Find someone with the skills or the money to develop your idea and sell them on WHY they should invest in you. And yes, this will mean giving up either a portion of the "ownership" or of future income or equity. And the more risk they have to take - the more equity they will want (and quite frankly be entitled to). 2. Learn how to code and build it yourself. MANY entrepreneurs without financial resources are still resourceful. They develop the skills needed to create what they don't have the money to pay someone else to do. 3. Get some cash so you can pay someone to do the coding. You'll probably have to have some knowledge of coding to direct the architecture of your idea. So you will likely still have to become knowledgeable even if its not you personally doing the coding. (This is not meant to be a comprehensive list of options... And I'm sure some of the other experts here on Clarity have others to add - and I hope they do) To wrap up - Here's my final tip to you that I hope you "get"... It's FAR more valuable to have an idea that a very specific hungry crowd is clamoring for right now - One that THEY would love and pay you for right now - Maybe even one they'd pre-order because they just have to have it - Versus YOU being in love with your own idea. [Notice I didn't say "an idea that some as-of-yet-undetermined market would probably love"] I wish you the best of luck moving forward.DB
-
How can I manage my developers' performance if I don't understand IT?
Whenever you assign them a task, break down the task into small chunks. Make the chunks as small as you can (within reason, and to the extent that your knowledge allows), and tell your devs that if any chunks seem large, that they should further break those chunks down into bite size pieces. For instance, for the overall task of making a new webpage, _you_ might break it down as follows: 1) Set up a database 2) Make a form that takes user email, name, and phone number and adds them to database 3) Have our site send an email to everyone above the age of 50 each week When your devs take a look at it, _they_ might further break down the third step into: A) Set up an email service B) Connect it to the client database C) Figure out how to query the database for certain users D) Have it send emails to users over 50 You can keep using Asana, or you could use something like Trello which might make more sense for a small company, and might be easier to understand and track by yourself. In Trello you'd set up 4 columns titled, "To Do", "Doing", "Ready for Review", "Approved" (or combine the last two into "Done") You might want to tell them to only have tasks in the "Doing" column if they/re actually sitting at their desk working on it. For instance: not to leave a task in "Doing" overnight after work. That way you can actually see what they're working on and how long it takes, but that might be overly micro-manager-y At the end of each day / week when you review the tasks completed, look for ones that took a longer time than average (since, on average, all the tasks should be broken down into sub-tasks of approximately the same difficulty). Ask them about those tasks and why they took longer to do. It may be because they neglected to further break it down into chunks as you had asked (in which case you ask them to do that next time), or it may be that some unexpected snag came up, or it may be a hard task that can't be further broken down. In any case, listen to their explanation and you should be able to tell if it sounds reasonable, and if it sounds fishy, google the problem they say they encountered. You'll be able to get a better feel of their work ethic and honesty by how they answer the question, without worrying as much about what their actual words are. Make sure that when you ask for more details about why a task took longer, you don't do it in a probing way. Make sure they understand that you're doing it for your own learning and to help predict and properly plan future timelines.LV
-
How do you manage a developer who's slow, especially when you have a small budget and you don't feel like you'll get things done in time?
Usually Programmers are only slow when they don't know how to solve a particular problem. So they will spend a lot of time researching and a lot of trial & errors to solve a problem. It is important that before you engage a programmer on a project, you break down the entire project into simple, easy to understand modules. Let him give you an estimate of how many hours he will require to complete each of the modules. Example: a typical site will have a login module, registration, My account, profile etc. So let him estimate how much he will require to do the login. You can go even detail here. (e.g. how much extra time if you were to implement Facebook/Twitter Login?). Once he start developing, track his progress closely and make sure he is following his given timeline. If he goes over his budgeted time on a module, talk with him and see what went wrong. It is often seen that they may be wasting their time on something very insignificant that you may have asked him to implement, but you can totally go by without it too. So by understanding what is taking longer time, you will be able to prioritise things better. You definitely need some tools to get this done. Google Spreadsheet or Excel works just fine. But if you don't mind spending a few bucks there are many agile project management tools that you might look into. Here is a list, google them all and sign up for trials: * AgileZen * Agile Bench * Assembla * AssiTrack * Blossom * Basecamp * Breeze * DoneDone * Eidos * Fogbugz * GreenHopper * Jugggla * Kanbanpad * Pivotal Tracker Or the reason why he is slow can be purely non-technical. Sometime your developer may don't share the same level of enthusiasm as you about the idea that you are working on. They often don't often see the "bigger picture" (since you don't share everything with them explicitly). If you can somehow get them excited about what he is a part of, it will work like a drug :) He will work day and night without questioning you. But you need to work equally as hard as him. The moment he sees that you are the boss and he is just the guy doing work for you -- his mentality will shift from being part of something to being the low paid developer. Ultimately its all about motivation and making him a part of your venture. After all he deserves it, if he is really playing a crucial role in the entire development.SK
-
What 3 questions to pose to a developer, to gauge his expertise level?
If you're not technical yourself, then you might not be able to gauge the efficiency of a candidate's algorithms or critique her code. But there are still some higher-level, more behavioral things that a non-technical interviewer should be looking for in a strong development candidate: 1. What are some tech blogs that you follow? Explain an interesting article to me that you read from one of them. The software development world changes all the time. Best practices are constantly evolving and new libraries are regularly released which make developers more productive. If a candidate doesn't keep up with the latest software news, that might be a red flag that they're not curious or trying to improve themselves. Also, having them explain a technical concept to someone who's non-technical is a great way to gauge their communication skills. Do they seem like someone you could work with and understand easily? Do they care about pausing to make sure you understand, or do they just drone on with jargon? If you feel overwhelmed while they're explaining this answer, imagine how you'll feel when they're telling you why the product has bugs or isn't going to be done on schedule. 2. Tell me about a time you ran into a big roadblock with something you were building. How did you get past it? It's inevitable that a software developer will get tripped up or have to solve some Gordian Knot. Everyone has to bang their head against the wall from time to time. Maybe an API didn't have the data they needed or some function was running too slow and they weren't sure how to speed it up. You're looking to see how they are as a problem solver. Did they come up with a clever but hacky solution? Were they methodical or did they fly by the seat of their pants? Did they go back to the stakeholders and see if the feature's requirements were flexible? Did they work on it for hours and hours trying new things? Did they ask for help from colleagues or on the internet? No right or wrong answers here, but you want to get the sense that this isn't someone who throws up their hands when they hit some friction. 3. Tell me about your favorite project that you worked on. What work are you most proud of? By asking them about the project they're most proud of, you'll get to see what it is that they value most. Maybe one candidate is most proud of a side project they built, even if it wasn't that technically complex, while another candidate is proud of their esoteric PhD project or some specific algorithm they improved. Again, no right or wrong answers, it really depends what type of candidate you're looking for. But it lets you see into their mind a bit, and get at some of the aspects that can make someone a strong development candidate. If you want to talk more specifically about hiring for your team, I'd be happy to do a call!HB
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.