Wallsync Capture
UX research & prototype (AcademyXi)

Wallsync Capture

WallSync is an app that Instantly transforms handwritten notes into Trello or Jira. Maintain your workshop's momentum to share outcomes with your team before they get back to their desks.

The Problem

Wall Sync is a relatively new app in the market, with many shortcomings but also with many growth opportunities. The Wallsync team requested our help to develop the existing application further but give it a much more human-centred approach.

Te team;- 3 Ux Designers - Founder

My role in the project:As the UX designer on the project, I worked on the user research and prototyping of the application. As a team, we conducted the user interviews, created user personas, sketching sessions. We also prototyped the main journeys of the portal to evaluate and validate our assumptions early in the process.

The tools;

  • Otter
  • Sketch/Illustrator
  • InVision
Wallsync mockup - High-fidelity prototype.

The Challenges

To educate the client on the value of research instead of working directly on just adjusting the graphical interface for improving the application.

The most significant challenge is that there wasn't a clear value proposition for the main user.

We also encounter a limited amount of time and budget besides other constraints such as confidential agreements. We decided to do 1 on 1 interviews with different user types in the search for our primary user.






The Plan

To validate the product value proposition with real users:
Initially, the platform was intended to scan the backlogs tasks written on post-its and send it to a management platform (Jira and or Trello) to facilitate the life of the Scrum Master.

the people interviewed were UX designers, BA, Product owners, and scrum masters.

We decided to implement the following strategy for the project:
A competitor analysis, user interviews, usability testing of the current App, User Journey, user workflow, and finally prototype the main journeys for usability testing purposes for validation.

Affinity Map, User Journey, MVP and Lean persona deliverables.

The Process

We conducted interviews/usability sessions with what we believe was our primary user. We encounter frustrating moments along the way; our hypotheses weren't being validated, and the time was less and less. Until we finally joined the dots.

We decided to open the user type, and started interviewing Designers, BAs and Product Owners.

We discovered that our users were not looking to scan or photograph wallboards. What users were looking for was an efficient way to document information without transferring the cost of that time to the client. This will allow them as well to focus on tasks that required more attention and have a higher priority.

We also discovered through the competitor analysis that the app had considerable market disadvantages. The app had usability problems used a less attractive visual design, and the development of the app wasn't as sophisticated as the ones compared.

Problem Statement:

As a Scrum Master, I need to put information into the digital format efficiently and accurately.

As a Scrum Master, I need this information to be shared and accessible for the team and myself.

We proceeded to create our user personas and user journeys based on these new insights. The Ideation process involved doing a rapid sketching session utilizing the crazy 8 exercises starting from crazy/bizarre ideas to the most minimalistic ones. We had a voting process from which I think we got the most appropriate approach to recommend to the client.

Wall Sync High-fidelity prototype.

The solution

We were able to improve the experience of the platform by refocusing the existing technology to a more suitable solution for the user.

Now, Scrum Masters, Designers, BAs and Product Owners can document their workshop in the format of their choosing and can share it with their team. We also improved the UI of the product following design heuristics and the UX writing associated with the education of use product (Onboarding, Buttons, FAQS, App messages, etc.)


I believe that it is essential to start a project with a precise understanding of the business objectives and what is the value proposition that the project is delivering. Not having a clear problem statement defined could affect your research and outcomes enormously.