A Conceptual Model created while working on a data retrieval solution, fully exploring the context of the tasks the solution intended to improve.
Intuitive user experiences and interfaces can only be designed with a clear understanding of who the user is, their goals, their motivations and their environment.
After conducting primary research consisting of interviews and observation User Experience Designers can distill and communicate what we've learned by creating Conceptual Models and Ecosystem Maps.
Mapping a workflow and identifying where and how a product could be introduced.
Converting this information into a visual, diagram form serves a few important purposes. It allows a team to build a consistent understanding of what their product does, and who for. Perceptions of a user and their world often vary with in product companies and teams, clarifying this unifies a team in it's direction and purpose.
Conceptual diagrams can uncover important opportunities for your company. By understanding what happens before and after the use of your product you can find ways to improve workflows or introduce solutions to issues you didn't know your users faced. Conversely, you can identify territory that you do not want to interfere with and carefully avoid.
Mapping an 'Ecosystem' of events, ideas and objects.
There are many good reasons for creating a Conceptual Model, but the most readily apparent is to understand what they think your product is for, how it works and why they use it. You can then manage your product's features, design and personality to match.