Implementing requirements in a way they are supposed to be implemented calls for detailed structured thinking and a robust execution plan. Avoiding this can be dangerous as slight gap in initial understanding can cause large deviation in end-result. It thus becomes important for product managers to define a clear path from requirement gathering till feature implementation. A path that is descriptive & self-corrective, path that eliminates false assumptions and ensures success at the end. I present here one such path, I call it path of 5 iees, it has helped me in recent past to deliver highly accurate requirements.
5 iees: Information, Interpretation, Intelligence, Implication, Implementation
Information: Information gathering requires you (as a Product Manager) to be constantly in touch with ground reality that helps in you in getting timely & accurate information (or still data maybe) on what probably may be your next killer feature. Practice being a social animal, a trail that is must for you to excel in knowing facts . I wrote about collecting requirements in my previous blog so I will just rush through this point.
References: Meeting customer || Information Radar || Social animal
References: Meeting customer || Information Radar || Social animal
Interpretation: Is knowing what actually you just collected (learned from various sources). If gathering information is like sweeping a broom on the floor then interpretation is like to know what to keep and what to let go in bin. Its imperative that you master this skill and get as accurate as possible. This is skill of make or break as small difference in initial understanding can translate into an out of place feature / product. Focus on every word you hear, drill down to facts and revisit your source of information to ensure you understand what you are expected to understand.
