Content
@
1 reply
0 recast
2 reactions
Elie
@elie
One of the main things I’m working on simplifying Inbox Zero. What have you found the best way to trim down a product?
2 replies
0 recast
10 reactions
Fran
@0x99fran
Existing features you are trying to remove? You need data on what features are used and by whom. You trim stuff that either isn’t used. Or is only used by non-target customers.
2 replies
0 recast
1 reaction
Elie
@elie
Ya. I think I’ll remove a feature today. Or at least hide it away so advanced users that are using it can continue to without confusing other people
1 reply
0 recast
1 reaction
Fran
@0x99fran
Thinking of your app in layers can be helpful. Intro layer, moderate user layer, advanced user layer. As important as features are, the order users discover them in can be important too. Hiding advanced functionality at a lower level can make the app more streamlined for onboarding without losing functionality
1 reply
0 recast
1 reaction
Elie
@elie
What’s an example of this in practice though? How do you reveal advanced features only for advanced users?
1 reply
0 recast
0 reaction
Fran
@0x99fran
Hmmm, An example of this would be taking the most popular sets of settings your users use and grouping the entire set into a much smaller set of default profiles. So maybe you take 20 setting and spit out 3 different “profiles” with predefined settings a new user can choose from. And then you leave a “custom” profile for advanced users to tweak
1 reply
0 recast
1 reaction
Fran
@0x99fran
So in this case the “intro layer” is your selection of initial defaults. The moderate user layer is the 3 different profiles someone can choose between, and the advanced layer is the custom profile.
1 reply
0 recast
1 reaction
