3 ms·
One of the things I've realized is that you basically need to design your technology to do exactly what the customer does. Once you've done that, you can start
by jon_richards 8y ago
One of the things I've realized is that you basically need to design your technology to do exactly what the customer does. Once you've done that, you can start cutting unneccesary stuff out and making stuff easier.
If you want to introduce a step that lets someone skip 2 steps, it's going to be a hard sell. Unless it's a critical part of your product, you should probably make it skippable. Otherwise people are liable to avoid it, falling back onto pen and paper, then run into trouble down the line when it prevents them from doing what they want.
- TeMPOraL 8y agoYeah. Assuming people are doing something just "because it's how they always did it" is a wrong approach. Your new 1-step process may let them skip 2 steps, but it may turn out they depend on the process being 2-step in order to e.g. handle special cases. This is what I often see happens with software, when someone tries to simplify the workflow by just looking at the most common sequence of actions and designing around that, and not minding all the flexibility they're throwing away that's crucial to handling uncommon cases. It's (one of) the reason people keep going back to Excel spreadsheets, even though your custom-tailored piece of software does everything they need better. It's because your system is rigid, and Excel spreadsheets are flexible.