Loading...
Answers
MenuTo keep or to discard features that aren't done correctly?
Answers
My vote is to kill it. Focus your team on what's important for your business. Just because it's done is not a reason to keep it.
I always think. If the feature is not helping the product achieve its primary goal, it most likely getting in the way of it.
It's really hard but keep your product focused and trim fat when possible. You and your Team should be ready for it. Clear goals help this process.
There's a few questions in your question.
1) Should you remove a feature if you know the other one is the right direction (and it'll be a departure from what you're offering right now)?
If it's hurting the customer experience, and doesn't work - then yes, take it out. If you don't think it will live on in the future, it's best to remove it and avoid confusing or frustrating new customers.
2) How do you avoid creating/shipping a half ass feature?
Well the good news is that you're probably the issue. The best way to nail a feature to ensure it's awesome is to spend the time up front iterating around different ways to solve it, usually in wireframes or mockups, and then prototyping using some app like Balsamiq (click-eable prototypes) or https://www.flinto.com/.
Ensure you get real copy, and user persona's with real data to play with and test the flows and all aspects of the user experience. If you spend the time up front developing these, then the engineers will work better and can't mix up what you're asking them to build.
So yeah, learn as much as you can about product management & marketing, and that should fix the issues.
P.S. These folks are geniuses when it comes to this
https://new.clarity.fm/sethberman/expertise/product-marketing
https://new.clarity.fm/cherylyeoh/expertise/branding-pr-product-marketing
https://new.clarity.fm/georgeishii/expertise/product-management
Hope that helps.
Sounds like you are getting bogged down in Slop which in this case stands for "Silly Loss Of Productivity" and leads to loss of profit.
I say, do the math. Where are you likely to make your money? Keep your eye on the ball that has $ signs on it. Make sure you are offering either products or services that lead to maximum profits. Make this or these your back-end products and services. Then add in products and services which are front end and even loss leaders. If you find yourself between two choices and you can't make a decision then choose both whenever possible.
Michael T. Irvin
NoHogWashMarketing.com
"Get To The Top Without The Slop"
michaelirvin.net
Related Questions
-
Is there any typical questions for customers' pain points discovery or it's impossible to standardise?
I have built several multi-million dollar businesses using (2) very simple questions: "What makes you say that...." and "Tell me more...." No matter what someone says to you, you just keep asking one (or both) of the questions. If you do it 4 or 5 times in a row you'll learn everything you ever wanted to know.DW
-
What are ways to find and engage B2B beta users for a brand new application?
Find apps that are B2B and go to the review sections. Specifically going to Google's play or Chrome store and look at reviews and follow them to Google+ to engage. I took that same angle for B2C app I was building last year. Check it out. http://blendah.com/post/37331434653/lean-startup-hackTM
-
What are some important milestones for a bootstrapped startup?
If you haven't fully tested your app with the 100 individual accounts Apple allows you to test via TestFlight or Hockey, then I'd suggest you should test thoroughly with your email list before launching to the app store. Things to look for at this early-stage: Activation and Breakage Points: From app download to user onboarding, where are people getting lost? Your goal is not only to have them download the app, but complete whatever steps for them to become your user. Optimizing the flow to ensure maximum conversion is a key first step. Engagement: How often are they completing the tasks you deem most important based on your business model? How can you increase this number? User Understanding: How clear is the app's UI and messaging? Where are they getting lost? Virality: While true virality is hard to measure at this stage (given the constraints of pre-launch testing), you can evaluate the potential effectiveness of any distribution tactics you might employ (contacts, OAuth's etc) in terms of user opt-in and conversion issues. Real analytical data is easier to interpret than user interviews but there is a such a treasure trove of good customer development intel from customer interviews. Those first 100 people who download the app should be personally interviewed about their experience, what they like, how much it solves their problem, how much of a problem that is for them in the first place and so on. Before you go live in the app store, I highly recommend you max out your installs in a private testing environment. I'm happy to talk this through with you in more detail in a call.TW
-
How can I smoothly transition from full time worker to self-employment?
The ways I've done this in the past are 1) Find some customers that are willing to hire you (or your product) but know that you'll only be free nights & weekends to support/work with them. 2) Find a "partner" (co-founder or other) that's got a flexible schedule that can help build the business while you're at work. 3) Block out nights, mornings and weekends to build the business till you have enough orders to cover 50% of your salary. This might mean 7pm-11pm most nights, and 4 hours each day Sat & Sun. Make progress (sales $$$) and momentum. All that being said, it's risk reward. Sounds like you want to avoid taken the risk, and I get that .. but the upside is always smaller. Unless you put yourself in a position to have to succeed (ex: quitting your job) then you may never make the scary decisions that are required to build a company (like cold calling, going in debt, making a presentation, etc). I'm on company #5 with many other side projects started nights & weekends .. so I get it - but don't be afraid to bet on yourself and go all in.DM
-
I'm having problems with ideation for a startup, I'm a web developer, what needs of yours aren't being met? Or how can I find a big problem to solve?
It's really ill-advised to solicit your vision from anyone. In my 20 years of building, investing and supporting tech companies, I don't know of a single success story that has it's origins in someone with your approach. Running a tech startup is incredibly hard. It demands sacrifices few are truly able to make and come with it tremendous risks that most people are unwilling to take. It sounds to me as if you want the startup life because you have an impression of what it's about but haven't yet experienced it first-hand. I'd encourage you to first join an early-stage startup. Developers are incredibly in-demand. Find an entrepreneur who has some experience, funding and a compelling vision that you believe in and get to know what the journey is really like.TW
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.