AS
← Work

MindMesh

A role-based micro-learning platform concept that helps non-technical creative users learn AI tools through personalized paths, modular lessons, and hands-on tool pages.

2025UX/UI Designer · Learning Experience DesignerFigma, User Research, Prototyping, Information Architecture, Learning Outcome Testing
UX/UI DesignLearning ExperienceWeb PlatformSenior Project

MindMesh is a senior UX/UI and learning-experience prototype for a web-based micro-learning platform. The project addresses a real adoption problem: non-technical creative users are not blocked by a lack of AI tools. They are blocked by a lack of structured, role-relevant guidance. The platform organizes AI tool learning around onboarding, personalized paths, modular lessons, tool pages, quizzes, progress feedback, and community support. It was developed across proposal, prototype, testing, and final presentation phases during 2024–2025.


The challenge

AI tools are increasingly present in creative and professional work, but the learning experience around them is fragmented. Non-technical users move between scattered tutorials, tool-specific documentation, social media tips, and trial-and-error. This creates a gap between curiosity and confident use: users may know a tool can generate images, automate content, or support ideation, but they do not know which tool fits their goal, what terminology matters, how to structure prompts, or how to apply the output inside a real workflow. MindMesh reframes this as a learning-experience design problem rather than an interface problem.

01
AI potential is visible
Designers, marketers, and students encounter AI tools through content work, visual ideation, and automation tasks.
02
Learning breaks down
Scattered tutorials, unfamiliar jargon, no clear starting point, and a lack of workflow-specific examples create friction before the first prompt is written.
03
Structure becomes the bridge
MindMesh addresses this by turning scattered AI information into guided, role-specific learning: paths, modules, tool pages, and progress feedback.
61.8%
cited complexity or coding knowledge as a barrier
Early survey findings
58.8%
reported difficulty integrating AI into their workflow
Early survey findings
47.1%
struggled to find tutorials relevant to their role
Early survey findings

Research signals

The project combined early survey work with 34 respondents, a final survey with 16 mixed-background users, two rounds of in-person testing, and a learning-outcome evaluation. Early findings pointed toward low confidence, terminology confusion, and a strong preference for step-by-step visual guidance. The final survey showed that 11 of 16 participants had never used MidJourney, Runway, or DALL·E, and average self-reported confidence was 2.3 out of 5. MidJourney was identified as the most confusing tool due to unfamiliar prompt syntax. These signals shaped the platform's learning structure from the outset.

Research evidence cards showing tool usage data, main barriers, learning goal preferences, and key takeaways from two survey phases and two testing rounds.
Directional research signals from early survey work, final survey feedback, and two rounds of prototype testing.

Learning preference gap

A key finding was the mismatch between what users currently experienced and what they actually needed. Most existing resources offered video-heavy general courses or scattered tutorials. Users consistently preferred step-by-step written guides, interactive practice, and real examples tied to creative workflows, in formats that existing platforms rarely combined in a role-specific way. MindMesh positioned itself to close that gap by organizing learning around roles, applied tasks, and practical tool scenarios rather than abstract AI theory.

Learning preference comparison chart showing current user experience versus MindMesh response across preferred learning formats.
Users preferred step-by-step guides and real examples, in formats most platforms did not deliver in a role-relevant way.

Learning architecture

MindMesh is designed as a learning system, not a content library. The core structure connects onboarding, path recommendation, modules, tool pages, practice tasks, progress feedback, and community in a single guided loop. Users enter through their role and goal rather than searching blindly across tools. Each path builds understanding progressively: from broad tool awareness through short modules to hands-on practice and self-assessment. The architecture keeps the relationship between learning paths and tool pages explicit, treating tool pages as extensions of the module journey rather than separate content islands.

Learning system map showing the full MindMesh architecture from onboarding through path recommendation, modules, tool pages, practice, progress, and community.
The platform connects onboarding, role-based paths, modular lessons, tool pages, practice tasks, and progress in one guided loop.

Platform structure

MindMesh offers three role-based learning paths: Design, Creative, and Marketing. Each path contains sequential modules focused on practical AI tool use within that role's workflow. Tool pages support hands-on practice beyond the module flow, providing tool-specific guides, prompt formulas, quick tips, use-case cards, and interactive quizzes. The Design path focuses on visual and motion workflows using tools like Runway, DALL·E, and Kling AI. The Creative path covers prompt writing and visual ideation through MidJourney and Firefly. The Marketing path addresses campaign content, social reels, and automation through Kling AI, Jasper, and similar tools.

Path and module structure matrix showing three learning paths: Design, Creative Marketing, with their modules, content types, and recommended AI tools.
Three paths, each with focused modules and recommended tools mapped to real creative workflow goals.

User scenario

To make the platform structure concrete, the design traces a real journey: Sarah, a junior designer assigned to explore AI for a campaign, logs in, completes onboarding, selects the Design Path, works through Module 1 (Tool Fundamentals) and Module 2 (Image Generation), applies what she learned in a tool page, and presents her output to the team. This scenario shaped onboarding depth, module sequencing, tool page layout, and the pacing of the overall learning flow.

Eight-panel storyboard following Sarah through getting assigned a visual task, completing MindMesh onboarding, receiving path recommendations, exploring modules, applying learning in a tool page, and presenting her work.
The storyboard traces a full session from task assignment through onboarding, module completion, hands-on practice, and team presentation.

User groups

The original project explored ten detailed personas. The portfolio version compresses these into five learner profiles that capture the real range of needs: the beginner who needs low-jargon, visual walkthroughs; the creative designer who needs prompt logic and tool comparisons; the marketing professional who needs applied campaign scenarios; the intermediate user who wants depth, shortcuts, and challenge cases; and the solo creator who needs simple, affordable AI workflows without complexity overload. The platform's onboarding questionnaire and level-tagging system respond to each of these needs within one product structure.

Audience and user segment matrix showing five learner groups: Designers, Marketers, Students, Small Business Owners, Curious Self-Learners, with their goals, AI experience level, and main needs.
Five learner profiles, each with a different entry point, goal, and design risk that the platform structure must address.

Testing and iteration

Testing moved in two distinct phases. The first round focused on usability: three design students completed early onboarding and module flows in person, revealing that navigation depth caused disorientation and that progress cues were not visible enough. This led to a simpler single-scroll layout and clearer progress indicators. A 16-participant online survey then identified terminology confusion as a second barrier, resulting in a glossary and simplified language across module content. The second round shifted focus to learning outcomes: whether users could understand tool differences, remember concepts, and apply them to practical scenarios, rather than simply navigating the interface.

Testing and iteration map showing four phases: Round 1 usability test, survey feedback, Round 2 learning outcome test, and iteration results with key design changes.
Testing moved from navigation and flow toward learning outcomes, with each phase producing concrete design changes.

Learning outcome results

The second testing round evaluated three participants with different experience levels. A beginner participant scored 4 of 6 on the learning check and showed improvement across the path, particularly in the Kling AI module. A mid-level user completed all six checks confidently but wanted deeper challenge-based content. An early-career creative scored 5 of 6 and directly connected the Kling AI module to a realistic social media workflow. Module clarity ratings averaged between 4 and 5 out of 5 across all three modules and tool pages. The strongest result was Module 3, which received a perfect score on clarity, reflecting a well-structured use case, visual output examples, and clear workflow relevance.

Learning outcome results dashboard showing overall 87% content recall, 4.6 out of 5 clarity score, 92% found content useful, participant scores, quiz performance, key observations, and next steps.
Prototype learning checks showed strong beginner and early-career clarity, with advanced users pointing toward depth as the next iteration priority.

Reflection

MindMesh is strongest as a learning-experience prototype: it connects onboarding logic, content architecture, modular tool practice, and outcome testing into one coherent product concept. The project's clearest success is showing that a structured learning path, rather than a tool directory, can help non-technical users build understanding and confidence with AI tools in a short session. The known limitations are honest ones: the prototype does not include a real content-management backend, advanced user depth needs further development, and a platform built around specific AI tools would need a continuous update model as tools evolve. If continued, the next step would be deeper challenge-based content for intermediate users, long-term retention testing, accessibility refinement, and defining how tool pages would stay current as the AI landscape changes.