Contact
Design Philosophy
Design Philosophy
I design therefore I am. I love to think up and apply paradigms to specifically take on challenging and complex problems, this approach helps me to ground and simplify my designs.
01
01
Landscape of Data
Landscape of Data
The information can be viewed at different levels of abstraction, and business consultants, who navigate complex problems, depend on shifting between these levels to make informed decisions. The challenge is that without careful design, presenting too much or too little detail at the wrong moment can obscure insight rather than reveal it. To address this, I conducted multiple rounds of research to uncover the behavioural traits and search habits of consultants. This informed the creation of a search workflow built around levels of abstraction, giving users access to the right depth of data at the right time. Inspired by examples like maps, which elegantly adapts what you see as you zoom in or out, this approach provides consultants with a familiar, intuitive way to explore data without losing context.
The information can be viewed at different levels of abstraction, and business consultants, who navigate complex problems, depend on shifting between these levels to make informed decisions. The challenge is that without careful design, presenting too much or too little detail at the wrong moment can obscure insight rather than reveal it. To address this, I conducted multiple rounds of research to uncover the behavioural traits and search habits of consultants. This informed the creation of a search workflow built around levels of abstraction, giving users access to the right depth of data at the right time. Inspired by examples like maps, which elegantly adapts what you see as you zoom in or out, this approach provides consultants with a familiar, intuitive way to explore data without losing context.
The information can be viewed at different levels of abstraction, and business consultants, who navigate complex problems, depend on shifting between these levels to make informed decisions. The challenge is that without careful design, presenting too much or too little detail at the wrong moment can obscure insight rather than reveal it. To address this, I conducted multiple rounds of research to uncover the behavioural traits and search habits of consultants. This informed the creation of a search workflow built around levels of abstraction, giving users access to the right depth of data at the right time. Inspired by examples like maps, which elegantly adapts what you see as you zoom in or out, this approach provides consultants with a familiar, intuitive way to explore data without losing context.
The information can be viewed at different levels of abstraction, and business consultants, who navigate complex problems, depend on shifting between these levels to make informed decisions. The challenge is that without careful design, presenting too much or too little detail at the wrong moment can obscure insight rather than reveal it. To address this, I conducted multiple rounds of research to uncover the behavioural traits and search habits of consultants. This informed the creation of a search workflow built around levels of abstraction, giving users access to the right depth of data at the right time. Inspired by examples like maps, which elegantly adapts what you see as you zoom in or out, this approach provides consultants with a familiar, intuitive way to explore data without losing context.
To give you an example, we can view maps in a similar way to the landscape of data.
Looking at the London Eye, we can see a park, paths, buildings and the pier on which the landmark sits on.
In this example, the London Eye could be a specific company. At a zoomed in level, the user will want data about the company such as what's their revenue over the past 5 years?



Zoomed our a little, now one can see the London Eye in relation to other landmarks such as Westminster Abbey.
Now, the user may see where the company is placed within the markets landscape. One can start to compare the company to its surrounding competitors and compare them.



Keep zooming out and you are looking at the city, viewing the meandering river, highways and green spaces.
Viewing the company at a high level of abstraction, one can grasp the global market landscape. Possibly understanding how international events can have significant implications to the company.



Understanding the levels of abstraction, I can help business consultants to carry out their research at the level suitable to them.
02
02
Progressive Disclosure
Progressive Disclosure
Business consultants face a unique challenge: they must process vast amounts of data to make informed decisions, yet showing all the information at once quickly clutters the screen and overwhelms the user. Even when searching for a single data point, consultants still need the surrounding context to trust its accuracy and relevance. The core problem is balancing depth with usability. To address this, I applied progressive disclosure principles. By structuring information in tier levels and enabling users to drill down only where needed, the design reduces cognitive load while still providing the comprehensive context consultants require.
Business consultants face a unique challenge: they must process vast amounts of data to make informed decisions, yet showing all the information at once quickly clutters the screen and overwhelms the user. Even when searching for a single data point, consultants still need the surrounding context to trust its accuracy and relevance. The core problem is balancing depth with usability. To address this, I applied progressive disclosure principles. By structuring information in tier levels and enabling users to drill down only where needed, the design reduces cognitive load while still providing the comprehensive context consultants require.
Business consultants face a unique challenge: they must process vast amounts of data to make informed decisions, yet showing all the information at once quickly clutters the screen and overwhelms the user. Even when searching for a single data point, consultants still need the surrounding context to trust its accuracy and relevance. The core problem is balancing depth with usability. To address this, I applied progressive disclosure principles. By structuring information in tier levels and enabling users to drill down only where needed, the design reduces cognitive load while still providing the comprehensive context consultants require.
Business consultants face a unique challenge: they must process vast amounts of data to make informed decisions, yet showing all the information at once quickly clutters the screen and overwhelms the user. Even when searching for a single data point, consultants still need the surrounding context to trust its accuracy and relevance. The core problem is balancing depth with usability. To address this, I applied progressive disclosure principles. By structuring information in tier levels and enabling users to drill down only where needed, the design reduces cognitive load while still providing the comprehensive context consultants require.
Information Architecture
Progressive disclosure only works if information is structured in a way that feels intuitive to the user. If categories are unclear or poorly organised, consultants won’t know where to drill down, leading to confusion and wasted time. To solve this, I focused on building a clear information architecture. Through research methods such as card sorting, I identified how users naturally group and prioritise data. This process not only supports progressive disclosure but also aligns with the mental models of consultants, ensuring they can quickly find and trust the information they need. This is by identifying different pain points and design restrictions and applying the same principles to them.
Progressive disclosure only works if information is structured in a way that feels intuitive to the user. If categories are unclear or poorly organised, consultants won’t know where to drill down, leading to confusion and wasted time. To solve this, I focused on building a clear information architecture. Through research methods such as card sorting, I identified how users naturally group and prioritise data. This process not only supports progressive disclosure but also aligns with the mental models of consultants, ensuring they can quickly find and trust the information they need. This is by identifying different pain points and design restrictions and applying the same principles to them.
Progressive disclosure only works if information is structured in a way that feels intuitive to the user. If categories are unclear or poorly organised, consultants won’t know where to drill down, leading to confusion and wasted time. To solve this, I focused on building a clear information architecture. Through research methods such as card sorting, I identified how users naturally group and prioritise data. This process not only supports progressive disclosure but also aligns with the mental models of consultants, ensuring they can quickly find and trust the information they need. This is by identifying different pain points and design restrictions and applying the same principles to them.
Progressive disclosure only works if information is structured in a way that feels intuitive to the user. If categories are unclear or poorly organised, consultants won’t know where to drill down, leading to confusion and wasted time. To solve this, I focused on building a clear information architecture. Through research methods such as card sorting, I identified how users naturally group and prioritise data. This process not only supports progressive disclosure but also aligns with the mental models of consultants, ensuring they can quickly find and trust the information they need. This is by identifying different pain points and design restrictions and applying the same principles to them.
03
03
Search Treads & Paths
Search Treads & Paths
Research is rarely a straight line. Yet most conversational search tools and legacy products force users into a rigid, linear flow. For business consultants, this creates friction: as they investigate data points, they often discover dead ends, shift perspectives, or backtrack to explore alternative angles. In a linear system, managing these detours becomes overwhelming, making it hard to retrace steps or maintain a clear train of thought. To solve this, I designed the concept of search paths, mini threads that branch off from the core search. This approach mirrors the investigative nature of real research, allowing consultants to explore freely while keeping their process organised, navigable, and easy to revisit.
Research is rarely a straight line. Yet most conversational search tools and legacy products force users into a rigid, linear flow. For business consultants, this creates friction: as they investigate data points, they often discover dead ends, shift perspectives, or backtrack to explore alternative angles. In a linear system, managing these detours becomes overwhelming, making it hard to retrace steps or maintain a clear train of thought. To solve this, I designed the concept of search paths, mini threads that branch off from the core search. This approach mirrors the investigative nature of real research, allowing consultants to explore freely while keeping their process organised, navigable, and easy to revisit.
Research is rarely a straight line. Yet most conversational search tools and legacy products force users into a rigid, linear flow. For business consultants, this creates friction: as they investigate data points, they often discover dead ends, shift perspectives, or backtrack to explore alternative angles. In a linear system, managing these detours becomes overwhelming, making it hard to retrace steps or maintain a clear train of thought. To solve this, I designed the concept of search paths, mini threads that branch off from the core search. This approach mirrors the investigative nature of real research, allowing consultants to explore freely while keeping their process organised, navigable, and easy to revisit.
Research is rarely a straight line. Yet most conversational search tools and legacy products force users into a rigid, linear flow. For business consultants, this creates friction: as they investigate data points, they often discover dead ends, shift perspectives, or backtrack to explore alternative angles. In a linear system, managing these detours becomes overwhelming, making it hard to retrace steps or maintain a clear train of thought. To solve this, I designed the concept of search paths, mini threads that branch off from the core search. This approach mirrors the investigative nature of real research, allowing consultants to explore freely while keeping their process organised, navigable, and easy to revisit.


04
04
Skeuomorphism
Skeuomorphism
Industry Reports
For business consultants, the challenge isn’t just accessing data, it’s interpreting it quickly and confidently. I observed that many of their most trusted resources, such as company and industry reports, share consistent patterns in structure and presentation. However, most search and results interfaces fail to mirror this familiarity, forcing consultants to reorient themselves every time. To solve this, I applied skeuomorphic design principles. By shaping the results experience to replicate the format of reports consultants already rely on, the interface presents information in a way that feels both intuitive and trustworthy. This reduces cognitive friction and allows users to focus on analysis rather than navigation.
For business consultants, the challenge isn’t just accessing data, it’s interpreting it quickly and confidently. I observed that many of their most trusted resources, such as company and industry reports, share consistent patterns in structure and presentation. However, most search and results interfaces fail to mirror this familiarity, forcing consultants to reorient themselves every time. To solve this, I applied skeuomorphic design principles. By shaping the results experience to replicate the format of reports consultants already rely on, the interface presents information in a way that feels both intuitive and trustworthy. This reduces cognitive friction and allows users to focus on analysis rather than navigation.
For business consultants, the challenge isn’t just accessing data, it’s interpreting it quickly and confidently. I observed that many of their most trusted resources, such as company and industry reports, share consistent patterns in structure and presentation. However, most search and results interfaces fail to mirror this familiarity, forcing consultants to reorient themselves every time. To solve this, I applied skeuomorphic design principles. By shaping the results experience to replicate the format of reports consultants already rely on, the interface presents information in a way that feels both intuitive and trustworthy. This reduces cognitive friction and allows users to focus on analysis rather than navigation.
For business consultants, the challenge isn’t just accessing data, it’s interpreting it quickly and confidently. I observed that many of their most trusted resources, such as company and industry reports, share consistent patterns in structure and presentation. However, most search and results interfaces fail to mirror this familiarity, forcing consultants to reorient themselves every time. To solve this, I applied skeuomorphic design principles. By shaping the results experience to replicate the format of reports consultants already rely on, the interface presents information in a way that feels both intuitive and trustworthy. This reduces cognitive friction and allows users to focus on analysis rather than navigation.
Pyramids of Data
Different stakeholders require different levels of detail, yet most data experiences present information in a one-size-fits-all format. Senior executives often need a high-level overview, while consultants may require key data tables, and subject-matter specialists want the full depth of analysis. Without a clear structure, catering to all these needs risks either oversimplifying or overwhelming the user. To address this, I drew inspiration from the natural hierarchy found in reports: executive summaries, key data highlights, and detailed explanations. By designing an experience around these existing levels of abstraction, I created a system that adapts to multiple audiences, offering each user just the right depth of information, without losing context.
Different stakeholders require different levels of detail, yet most data experiences present information in a one-size-fits-all format. Senior executives often need a high-level overview, while consultants may require key data tables, and subject-matter specialists want the full depth of analysis. Without a clear structure, catering to all these needs risks either oversimplifying or overwhelming the user. To address this, I drew inspiration from the natural hierarchy found in reports: executive summaries, key data highlights, and detailed explanations. By designing an experience around these existing levels of abstraction, I created a system that adapts to multiple audiences, offering each user just the right depth of information, without losing context.
Different stakeholders require different levels of detail, yet most data experiences present information in a one-size-fits-all format. Senior executives often need a high-level overview, while consultants may require key data tables, and subject-matter specialists want the full depth of analysis. Without a clear structure, catering to all these needs risks either oversimplifying or overwhelming the user. To address this, I drew inspiration from the natural hierarchy found in reports: executive summaries, key data highlights, and detailed explanations. By designing an experience around these existing levels of abstraction, I created a system that adapts to multiple audiences, offering each user just the right depth of information, without losing context.
Different stakeholders require different levels of detail, yet most data experiences present information in a one-size-fits-all format. Senior executives often need a high-level overview, while consultants may require key data tables, and subject-matter specialists want the full depth of analysis. Without a clear structure, catering to all these needs risks either oversimplifying or overwhelming the user. To address this, I drew inspiration from the natural hierarchy found in reports: executive summaries, key data highlights, and detailed explanations. By designing an experience around these existing levels of abstraction, I created a system that adapts to multiple audiences, offering each user just the right depth of information, without losing context.
05
05
Connective Tissue
Connective Tissue
Search may be the core feature of the product, but it cannot exist in isolation. If designed without consideration for its relationship to the broader ecosystem, the result is a fragmented experience, users lose their workflow, and the product fails to support their goals end-to-end. To solve this, I developed the philosophy of connective tissue: designing search as both a hub and a bridge. Sometimes this means pulling complementary features directly into the search experience; other times, it means enabling seamless transitions from search into other parts of the product. By weaving these connections intentionally, search not only becomes more powerful on its own but also elevates the entire ecosystem.
Search may be the core feature of the product, but it cannot exist in isolation. If designed without consideration for its relationship to the broader ecosystem, the result is a fragmented experience, users lose their workflow, and the product fails to support their goals end-to-end. To solve this, I developed the philosophy of connective tissue: designing search as both a hub and a bridge. Sometimes this means pulling complementary features directly into the search experience; other times, it means enabling seamless transitions from search into other parts of the product. By weaving these connections intentionally, search not only becomes more powerful on its own but also elevates the entire ecosystem.
Search may be the core feature of the product, but it cannot exist in isolation. If designed without consideration for its relationship to the broader ecosystem, the result is a fragmented experience, users lose their workflow, and the product fails to support their goals end-to-end. To solve this, I developed the philosophy of connective tissue: designing search as both a hub and a bridge. Sometimes this means pulling complementary features directly into the search experience; other times, it means enabling seamless transitions from search into other parts of the product. By weaving these connections intentionally, search not only becomes more powerful on its own but also elevates the entire ecosystem.
Search may be the core feature of the product, but it cannot exist in isolation. If designed without consideration for its relationship to the broader ecosystem, the result is a fragmented experience, users lose their workflow, and the product fails to support their goals end-to-end. To solve this, I developed the philosophy of connective tissue: designing search as both a hub and a bridge. Sometimes this means pulling complementary features directly into the search experience; other times, it means enabling seamless transitions from search into other parts of the product. By weaving these connections intentionally, search not only becomes more powerful on its own but also elevates the entire ecosystem.
Check out my other notes
HS
HS
HS
HS