3 ms·
As someone who has been a product engineer and internal tool engineer I really appreciated that they made the distinction. Some other points to think about. 1.
by arthurjj 12y ago
As someone who has been a product engineer and internal tool engineer I really appreciated that they made the distinction. Some other points to think about.
1.In the first version of the tool don't have the tool make a decision, just have it generate information, not make decisions. So if it is telling you which sales lead to pursue, first have it generate metrics on why you should pursue a lead
2. Once you have a tool that makes decisions always have a way to let a human override the tool's decision
3. Start with a process then add a tool. It's almost always either to work out bugs with people then software
- noahbrier 12y agoNoah here from Percolate. I agree and what's interesting is I also think these are pretty classic values for enterprise (or b2b) software in general. Without the centralized data it's really hard to build any of the workflows or other tools.
- arthurjj 12y agoAgreed. That's why I like to start with a process and then build a tool. If people find the process valuable enough to follow it then you know the tool will be providing real business value