> zero work done Knowing what should and should not be implemented (where to go) may be more important than being able to move in random directions. Once requ

> zero work done Knowing what should and should not be implemented (where to go) may be more important than being able to move in random directions. Once requirements are clear, the implementation becomes easier. Perhaps, the guy should be in the product team, not in devs.