Feature stub

Type

Versatility

Definition

The feature stub method is a low-cost and quick way to gauge user interest in a potential feature before investing time and resources into building it.

Things to keep in mind:

• Be transparent: Let users know that the feature is not yet available and that you are just testing the concept. Set clear goals: What do you hope to learn from the experiment? What metrics will you use to measure success?
• Don't over-engineer the stub: The goal is to test the concept, not to build a perfect replica of the feature.

Example

You're a ride-hailing app and want to test a new feature that allows users to schedule rides in advance. Instead of developing the entire feature, you can run a feature stub experiment as follows:

• Design a "Coming Soon" placeholder: Add a button or link within your app that says "Schedule a Ride (Coming Soon)" or offers similar messaging.
• Promote the new feature subtly: Mention the upcoming scheduling feature in announcements, blog posts, or social media content, generating some awareness.
• Track user engagement: Monitor how many users click on the button, sign up for a waitlist, or provide feedback through surveys or comments.

From this experiment we can learn:

• Interest level: The number of users interacting with the stub indicates potential demand for the feature.
• Early feedback: User comments and reactions can reveal preferences, concerns, and desired functionalities for the actual feature.
• Prioritization: Based on interest and feedback, you can decide whether to prioritize this feature for development or focus on other initiatives.