My experiences facilitating Software Product Development and Operations

Source: https://www.flickr.com/photos/ralphpaglia/8316453365 Initially during conceiving a concept the terminology used to describe the entities, processes and methods are usually approximate. It all depends on the level of skill, knowledge and experience among the teams. As the concept gets clearer the appropriate and right items are identified and assigned. Sometimes a new non-existent technical or business or 'whatever- closely-resonates ' terminology gets framed to address the immediate communication needs . This journey to attaining clarity and obtaining general acceptance is an interesting part of product building. However, it results in interesting situations with categories of terms being used during communication though the intentions are benign Misguiding terms – They are likely to convey the wrong requirement or the solution Incorrect terms – They do not convey anything about the requirement or the solution References – i.e. They convey ...

The role of User Interface Design and User Experience are paramount these days with plethora of applications in all segments. Hence, there is lot of emphasis on including UI and UX aspects right from conceptualizing the solution for a problem. However, the amount of detail included in the initial User Interface (UI) concept for discussion, popularly referred to as a ‘wireframe’, may negatively influence the outcome of the final product i.e. it’s utility The Problem - More detail is better for conveying ideas Product Managers/Product Owners usually visualize their ideas primarily through approximate or rough sketches depicting the UI called ‘Wireframe’, the expectation being that the ideas expressed in the UI will quickly result in gaining consensus and implementing a solution . Some product owners are very imaginative and handson and like to share ideas visually while others are happy sticking to conveying ideas verbally. With multiple affordable subscription tools such as Vis...