the startups.com platform about startups.comCheck out the new Startups.com - A Comprehensive Startup University
Education
Planning
Mentors
Funding
Customers
Assistants
Clarity
Categories
Business
Sales & Marketing
Funding
Product & Design
Technology
Skills & Management
Industries
Other
Business
Career Advice
Branding
Financial Consulting
Customer Engagement
Strategy
Sectors
Getting Started
Human Resources
Business Development
Legal
Other
Sales & Marketing
Social Media Marketing
Search Engine Optimization
Public Relations
Branding
Publishing
Inbound Marketing
Email Marketing
Copywriting
Growth Strategy
Search Engine Marketing
Sales & Lead Generation
Advertising
Other
Funding
Crowdfunding
Kickstarter
Venture Capital
Finance
Bootstrapping
Nonprofit
Other
Product & Design
Identity
User Experience
Lean Startup
Product Management
Metrics & Analytics
Other
Technology
WordPress
Software Development
Mobile
Ruby
CRM
Innovation
Cloud
Other
Skills & Management
Productivity
Entrepreneurship
Public Speaking
Leadership
Coaching
Other
Industries
SaaS
E-commerce
Education
Real Estate
Restaurant & Retail
Marketplaces
Nonprofit
Other
Dashboard
Browse Search
Answers
Calls
Inbox
Sign Up Log In

Loading...

Share Answer

Menu
Customer Development: To keep or to discard features that aren't done correctly?
Dan Martell, SaaS Business Coach, Investor, Founder of Clarity answered:

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.

Talk to Dan Upvote • Share
•••
Share Report

Answer URL

Share Question

  • Share on Twitter
  • Share on LinkedIn
  • Share on Facebook
  • Share on Google+
  • Share by email