A Meaningful Journey, in the context of designing Web and mobile apps on an AI-powered No-Code Platform is one of four Design Principles we apply at Being Guided. Our other, interrelated Design Principles are Fierce Reduction, Progressive Disclosure and Vibe Coding.

Knowledge-intensive organizations in market-facing sales and marketing mode rely on software to manage complex tasks, streamline processes, and facilitate decision-making. However, user adoption of these tools often lags due to poor design, lack of relevance, or resistance to change.

A Meaningful Journey addresses these challenges by prioritising User Experience (UX) in software design, ensuring that apps are not only functional but also engaging and aligned with users’ goals. This applies to No-Code Platform technologies I work with at Being Guided.

There is an important concept applied to creating a Meaningful Journey with Web and mobile apps: in the jargon it's called Uniform Connectedness¹. This is where the elements that make up a screen are connected by uniform visual properties.

Gestalt Principles, Applied

Uniform Connectedness borrows from six commonly recognised Gestalt Principles of Perception²: Similarity; Continuation, Closure; Proximity: Figure/Ground; and, Symmetry/Order (also known as 'Pragnanz'). Let's interpret these six elements, as it's applied to User Experience (UX) Design:

Similarity: Using consistent button styles and color schemes across components, so users intuitively group related actions like "Save" or "Submit" based on their shared visual traits. This reinforces familiarity and streamlines interaction within the ecosystem.

Continuation: Aligning form fields and navigation menus in smooth, unbroken lines, guiding users’ eyes naturally through workflows, such as filling out a record or exploring a sidebar, without abrupt interruptions.

Closure: Applying icons, like a partially open envelope for email notifications rely on users’ ability to mentally complete the shape, making the interface concise yet instantly recognizable.

Proximity: Grouping related elements, like a product name, price, or 'Add to Cart' button, close together on e-commerce pages, signaling their connection and enhancing usability.

Figure/Ground: Employing contrasting backgrounds, such as a white card against a grey backdrop, to distinguish actionable items (Figure) from the surrounding layout (Ground), helping users focus on key tasks like editing a record.

Symmetry/Order: Balancing layouts, like symmetrical dashboard grids, to clearly create an orderly appearance, making complex data feel approachable and reducing cognitive overload for users with Web and mobile apps.

Maximising User Experience

Research shows that user-centric design significantly improves adoption rates. According to the Technology Acceptance Model (TAM), perceived ease of use and perceived usefulness are key predictors of software adoption (Davis, 1989³).

A Meaningful Journey builds on this by creating experiences that are not only usable but also emotionally engaging, fostering long-term user commitment.

Design Thinking, Applied

In aligning a Meaningful Journey with a more simplified, digitised sales process having a familiar User Experience with an AI-powered No-Code Platform, is also where we apply Design Thinking, as set-out by the The Hasso Plattner Institute of Design at Stanford University (commonly known as d.school) based at Stanford University⁴.

The Stanford d.school Design Thinking method provides six (6) iterative stages for our digital innovation with No-Code First engagements: Empathize; Define; Ideate; Prototype; Test; and, Implement.

Stage 01. Empathize

Objective: Understand the users and their needs.

User Research: Use techniques such as interviews, surveys, and observations to gather insights into the users' experiences, preferences, and pain points. Focus on individuals who work in knowledge-intensive environments to relate specifically to your target audience.

Personas Development: Create user personas based on research data that represent different segments of your audience. This helps in visualising who you are designing for and understanding their motivations, goals, and challenges.

Stage 02. Define

Objective: Clearly articulate the problem you are trying to solve.

Problem Statement: Synthesize the insights gathered during the Empathize phase to define a clear and concise problem statement. Adjust this to reflect specific issues faced by users in managing their projects and tasks on a No-Code First app.

User Journey Mapping: Create a visual representation of the user’s experience from screen to screen, identifying the touchpoints where users interact with the app. This helps highlight areas of friction and opportunities for improvement.

Stage 03. Ideate

Objective: Generate a wide array of ideas to address the defined problem.

Brainstorming Sessions: Encourage team members to brainstorm solutions without constraints. You can use techniques like mind mapping, sketching, or collaborative digital tools to generate ideas.

Prioritisating Ideas: Filter the generated ideas to identify the most feasible and impactful solutions. Consider factors such as user needs, technical feasibility, and strategic alignment with business goals.

Step 04. Prototype

Objective: Create low-fidelity representations of your ideas.

Rapid Prototyping: This where we emphasis No-Code First and make use of the standardised No-Code First innovation for all apps and all devices.

Storyboards: Develop storyboards to visualise the user flow and interactions through key screens. This helps in illustrating how users will navigate the app and what choices they will make.

Step 05. Test

Objective: Validate the usability and effectiveness of your solutions.

User Testing: Conduct usability testing sessions with real users to gather feedback on the Prototypes. Observe how users navigate through the app and identify pain points.

Iterative Reflections: Collect qualitative and quantitative data from testing to refine your designs. Encourage users to express their thoughts about the experience. Focus on what worked and what didn’t.

Step 06. Implement

Objective: Bring your solution to life and launch it to users.

Agile Development: Work collaboratively with developers to ensure that the design is accurately translated into a functional application.

Continuous Improvement: After the launch, continue monitoring user feedback and engagement metrics. Make data-driven adjustments to enhance user experience continually. Set up mechanisms for ongoing user feedback to adapt the app to evolving user needs.

References

1. Palmer, S. and Rock, I. (1994). Rethinking Perceptual Organization: The Role of Uniform Connectedness. Psychonomic Bulletin & Review, vol. 1, p. 29-55. https://link.springer.com/article/10.3758/BF03200760
2. Wertheimer M. (1912). Experimentelle Studien über das Sehen von Bewegung. Zeitschrift für Psychologie. 1912;61:161–265.
   https://pmc.ncbi.nlm.nih.gov/articles/PMC3482144/
3. Davis, F. D. (1989). Perceived usefulness, perceived ease of use, and user acceptance of information technology. MIS Quarterly, 13(3), 319-340.
   https://doi.org/10.2307/249008
4. The Hasso Plattner Institute of Design. (2004) Stanford d.school. https://dschool.stanford.edu/about