At talPor We’ve been running remote UX consulting sprints and want to share what we built and learned in the process.

We work with Startups and companies around the world to create products that people love to use. It is usually a demanding job but it leads us to constantly be in the development of new methodologies and experiments to help our clients from the birth of their projects to achieving their goals and success.

That is the main reason why we created a UX consulting service, a new approach that allows us to transform our clients into co-creators throughout the entire product construction process and provide them with modern tools and technologies to align with their business strategies, the real needs of its users and eliminate obstacles in the work process.

In general, our work proposal during the consultancy covers the following points:

Objective: Co-creation sessions for a deep understanding of the needs and insights of users, business and feasibility.

Result: People profiles, Priority map, Brand attributes.

Objective: We conceptualize insights and seek to create powerful ideas that generate value for both business and people.

Result: Information architecture, Definition of graphic line.

Objective: We validate concepts and hypotheses with the end user and iterate to obtain the ideal solution.

Result: Wireframes, low-fidelity prototype, user stories.

Objective: We make learning tangible and we design the interface to take it to testing and production.

Result: Complete interface, assets, high fidelity prototype.

This is not the first time that we have used UX methodologies to help Startups and companies develop better digital products. To mention a few, we recently worked hand in hand with Procter and Gamble to design a mobile app that tracks the menstrual cycle and in turn helps to gain insight into the use of its products and the possibilities for improvement.

We have also made use of a wide range of tools and methodologies with Xara Cloud in the last year to improve the experience of using the web app and create new solutions.

One of the most important points to highlight about this methodology is being able to involve our team in work sessions with stakeholders, key project members (that is, decision makers), and at least one person outside the target.

The discovery phase (or stage) of the project is when we analyze the market and the target user, define product adjustments thinking about the real needs of the market and gather all the requirements and objectives of the project.

As a result, the discovery stage helps to better organize the development process and connect customers’ business goals with the needs of their users.

For this stage we decided to use the Miro tool to document and streamline sessions collaboratively and online. After each session we share via Slack the minutes of the meeting and a brief summary in video format using Loom.

The objective of this session is to understand in depth the context and the needs of the actual and potential users of the product to be developed. The most important data to investigate are:

The second session consists of discovering the purpose of the brand to build a product allied with the attributes of communication and impact. We analyze the following aspects: Culture, co-creators, voice, feelings, impact and what sets them apart from the competition.

Determining the focus of the product, key functionalities and creating a map of priorities to implement, is essential to prepare a development roadmap and provides clarity while aligning efforts.

This session was created under a Design Thinking approach to speed it up, however it was guided by one of our development specialists, who would later be in charge of leading the implementation at the code level and the technical team.

Ideation stages usually seek to generate many ideas that then inspire to create some better ones or encourage innovation.

In our case, we try to be more concrete and we start from the idea of creating a collaborative process that helps us not only to generate ideas, but also to approve them more clearly. That process is the construction of Stylescapes.

The biggest challenge is to translate the ideas that are in the client’s mind to translate them into a sensible and coherent graphic line.

We seek, then, to define at this stage the look and feel of the product and to begin assembling the structure.

The main objective of this stage is to validate the strategy, architecture and navigation of the product.

We usually create a Prototype in Figma or Sketch and make it navigable in inVision. We can summarize this stage like this:

It may be, for example, that you want to validate a specific module of the application, study if the navigation is intuitive enough or discover if users quickly understand what a button is for.

Once the route is clear and the initial ideas have been validated, the complete interface design is launched and development work begins in parallel to make real what until now is only design.

The life cycle of this stage is quite direct, but it can be cyclical if the product requires it. For example, a web or mobile app is usually in constant evolution.

It is quite common for startups and large corporations to encounter obstacles in workflow and decision making. That is why more and more companies contact us about our experience in product design and development, our strategies to improve workflow and our product definition processes.

Making an impact on people’s lives through a digital product is based primarily on creative problem solving to spread the story. However, I want to focus this on 3 main aspects for which this methodology is effective.

All writing