This chapter covers lessons on how to improve your product and the value you provide. It’s useful for the CEO and CTO.
Half-ass one thing many times.
Because that means you didn't spend time on something that isn't useful.
Don't ask an accountant about routing algorithms.
When you are observing users interacting with your app, they take on a different persona
Listen closely to their feedback because they are actively looking for a solution to a problem.
Help the user do what they want, or make the user do something you want. Try to do mainly the first.
It makes you build poorly thought out and potentially wrong things.
They should be given a similar level of attention as your external users.
That way main user data won't be polluted, but you'll still have a window into what the admins are doing.
Instead of redesigning standard features, pick comparable role models and copy theirs.
Software is a supporting component in a process that accomplishes something useful more efficiently than others.
In particular, consider whether new things you're working on can destroy what you've already built.
Sometimes creating the opposite interaction can have an even more powerful effect
That dashboard would show all and only the information and actions that they need.
Make sure that you know all the benefits of what you're selling, not just what you intended.
To effectively communicate with your team and customers, you must learn the correct jargon and use it consistently.
They're not just about control but also a tool to design a simpler and less error-prone product.
Include the ability to select start and end dates, period lengths, and the number of periods prior and following.