2 ms·
Hello, fellow product owner! We truly understand the product and the effort needed to get there but we're inherently not detail oriented and once we've "solved
by kthejoker2 8y ago
Hello, fellow product owner!
We truly understand the product and the effort needed to get there but we're inherently not detail oriented and once we've "solved the problem" with that 40% pilot/MVP we tend to get bored with the implementation details and we certainly become "idea guys" if we don't at least keep piloting new features and being honest with ourselves about the externalities our ideas create.
Anyway as long as you're being thoughtful about the relationship between your idea, the actual code, and the actual user experience, you can avoid being just an idea guy.
- ggm 8y agoHello fellow human! I think you have the right of it: the inability to cut code for long-term dependency doesn't mean you can't play a role, it's just that you have to be clear what the role is. I suspect what somebody else would say in a specification, I find easier to explain by example. So far, the real code warriors seem ok with this.