Why we built eProduct
We built eProduct as an Evidence-based product management solution that enables product managers and startup founders to understand, prioritize and deliver what customers need based on market data.
eProduct solves the product teams 3 major problems we just described.
1. It helps them understand customer needs. Understand the what and they why.
For every feature, enhancement or product, product teams are a click away from the evidence to back their decision. What users ask for, how many, what market, what type of customers, which vertical, and most importantly a documented record of why they asked for it. So when time comes to justify their ROI, they have the data.
Unlike current disconnected silos, eProduct becomes the single source of truth for the product. All this information is now in one system, presented in an easy way that can easily be filtered, sorted, and tabulated.
e.g. So when Management asks them… who asked for 2FA? What verticals are they in, and what are the top 5 customers who want it?
Or, the board asks them… what are the top 10 requests by Bank of America across, enhancements, high priority bugs and commits? – this one is fun to compile with existing methods!
They can quickly share a view with the answer in less than a minute.
So eProduct enables product teams to clearly understand customer needs, what they want and why
2. Now that product teams have everything in one place, understand what customers need, they can easily prioritize with confidence and quickly know what to build next based on market evidence and a known process
Prioritizing in eProduct is simple and flexible. Teams can use any prioritization model that fits their business need and choose the scoring technique or ranking criteria that works for them.
Teams can build custom views and share them with stakeholders.
When prioritization done right, delivery becomes easier, because
3. Product teams are delivering on customers needs in the right sequence needed by the market
What’s more, they don’t get distracted by last minute requests because they have a simple, yet powerful process, an easy to use and understand system to manage the whole process.
eProduct provides Product teams with the data to engage and collaborate with their constituencies, at the same time the confidence to push back when needed and deliver based on market data
So how did we do that?
eProduct is Like Salesforce for product teams
Teams manage the product management lifecycle from ideation all the way to product launch. Just like salesforce managing the whole opportunity lifecycle.
In each step of the lifecycle they have tools to collaborate and engage with their stakeholders and customers:
Ideas submissions, voting and suggestions – in the understanding phase to engage customers, prospects and users
Jira integration and collaboration with internal parties and development teams as they are building the product. Custom views and reports to share with management, and other stakeholders to rally them behind the vision and roadmap
Build and execute product launches with ease and engage with different teams for a successful product launch
Similarly, we are building integrations with Jira, Intercom, Salesforce, Marketo and others to help automate tasks for an easier flow.
A. It starts with a familiar and simple way to define and build their universe.
As simple as File explorer or email folders, Teams can create a hierarchy that makes sense for their business in order to track everything in one place.
Unlike existing solutions where you can manage only specific items, and everything else is an HTML note/document;
eProduct is different, it treats everything as an object, a record that has metadata. A record that can be ranked, moved, sorted, referenced, etc.
For example, You can create a folder for strategy, another for roadmaps, and a 3rd for product launches.
You can build unlimited hierarchy to fit your business needs
Each node represents a list of records, eg. customers, user personas, markets, features, ideas, bugs, or any other object you want to track.
Let’s take features for example. Existing tools create a list for features, a list for epics, and another stories, you always wonder how things relate, and you miss the big picture we talked about. eProduct is different,
B. it allows teams to build a list of hierarchical items to get context.
Teams can build a hierarchical list of related records such as epics, features, stories and tasks and get the full picture in one view. Of course they can filter, sort, group and do all sorts of things to narrow down to what they are looking for. Or just do a simple search
Another example for this hierarchy is product launches. How many times we tried to twist a spreadsheet to have categories because we like spreadsheet columns but we lack hierarchy and structure; or use OneNote or other tools that have flexible hierarchy, but lack columns, sorting and metadata. Well eProduct gives you both hierarchy, and columns/metadata.
If the user doesn’t find an object type, she can create it on the fly based on permissions. It took Aha!, one major competitor 2 months to introduce a new object called master feature. With eProduct, users can create it themselves in 30 seconds.
Which brings me to the third component, which is user defined fields
C. eProduct allows a rich user defined fields that can be added on the fly based on permissions
These are rich fields like ranking, rating, drop-downs, related records, formula and more.
Teams can group, sort, filter and search by any custom field
Think of a feature, you might want to know which user persona, which market, what is the effort, the market impact, the calculated score, how it stacks against a competitor, which vertical needs it, etc. you can see all of this in one screen with ease.
The cool thing is that you can zoom in on the priorities you want based on any or a combination of these criteria and save it as custom view that you go back to anytime or share with your stakeholders.
D. Link records is a great way to back your records with data in other records as explained earlier. I want to know for this feature, which customers ask for it. Or which ideas were submitted, or customer requests or escalations for this feature. I can easily link a record to one or multiple records in one or multiple lists.
Each of these features is not unique, however the combination is outstanding.