Empowering the Office 365 Experience

Seamlessly Translate, Effortlessly Communicate!
Product design
Customer

Lengoo

Product

Web and desktop
plug-in for office 365

My role

- User research (Interviews)
- UI kit design
- User Flows

Time scope

January-February 2023

What was the problem?

- Users wanted to have instant translations and leverage the usage of their language resosurces to have better short translations without the need of having to go through a long requests  process.

- They also wanted to speed up their working time and  translate instantly from the apps they use for their daily tasks without having to switch screens.

My solution

- Expanding Flow to an “Plug-in” for the office suite where they can use their translation memories to translate inside their work apps.

What is "Flow"?

Flow represents a cutting-edge instant translator harnessing custom machine translation memories to deliver sleek and personalized brand translations. Tailored for seamless cross-functional communication across diverse language-speaking teams, it's not just a translator—it's a language fusion tool.

Putting business requirements in context
Responding to our customers' demand, we integrated Flow into Office 365, empowering users to translate work-related texts, files, and emails without missing a beat.
I spearheaded the user research and injected a cool factor into the UI design for the inaugural version of this game-changing plug-in.

💎 DISCOVER

While conducting user feedback calls for the primary instant translator, we observed users expressing a desire for a more accessible translation interface. To gain deeper insights into their needs, we collected additional information.

1. User personas - Shaping our target audience
We have conducted User Interviews to get a better understanding of the users’ need, goals and build the user personas.  We created a series of questions, that lead update our previous user persona.
What impressed me the most is that speed is an important factor for them for translation tasks, as long as it doesn't compromise the final quality. We interviewed 4 participants.

Jeffrey Proser

❤️ Frustrations

-Compromising quality over speed
-Correcting language assets repeatedly
-Jumping between apss at work

🫠 Motivations

- Control on language assets
- Saving time on admin tasks
-Delivering high quality at work

As an Expert Translation Manager in a corporate setting, he prioritizes the translation quality, as it shapes inter-language communication among colleagues. Outside work, he enjoys spending time with his kids and delving into literature on diverse cultures.

2. Sculpting the path for our audience
I crafted User Journeys for the User Persona, offering a comprehensive view of their interaction with the product—from composing text to its ultimate use in various contexts like emails, marketing communications, and documentation.
3. A Comprehensive Analysis of Key Market Players
I reviewed what was the current state of Add ins on the office suite, and most importantly for 5 instant translators. In total i had 9 Examination points between, text translation, document translation, replacement of texts among others.
Here is a summary of the  two most that had the most important insights based on user’s insights:
Microsoft translate
💜 Positive points

- Translation monolingual section text
- Translation of entire document
- Replace source with translated target
- Auto-detection of source language

😬 Negative points

- They user cant paste the target translation and keep the source one
- There are no shortcuts to start the plugin
- Selection of memories to perform translation

Systran
💜 Positive points

- Translation monolingual section text
- Translation of entire document
- Replace source with translated target
- Autodetection of source language
- Selection of memories to trigger translation

😬 Negative points

-They user cant paste the target translation while keeping the source one
-There are no shortcuts to activate the plugin

🫶🏽 EXPLORE & DEFINE

4. Some last interviews before starting to design
We needed to gain better insight on what features and functionalities were crucial to our users. I conducted user interviews to have a deeper understanding. The biggest surprise was that they didn’t want to have a complicated UI, just a tool that could speed up their processes.

Some of the questions

- Which app from the suite do you use the most?

- What are your translation painpoints?

- Between translating existing content and producing it, which activity do you do the most?

- Which kind of features from flow would you like to see in the Plugin that could help you to be faster?

- What do you translate the most? (Portions of text or entire documents)

- What feature help you the most for your work and why? (Translating and keeping the source text or, replacing it?)

The findings

When i had all the necessary insights from the research part, me and the product team created the problem statement that would guide us during the design process.

They use outlook, word, and excel the most.

Translation of snippets of texts and entire documents are equally important for them.

The most important features for them to include were selection of languages, document translation, translation of existing text and free writing translation.

Crafting a problem statement and developing user stories proved instrumental in creating my solution's purpose and objectives. This process not only ensured clarity but also solidified the value proposition for users, fostering sustained engagement over the long term.
5. Pain points to address with my solution
Detected pain points

🔒 Data security:
Translation data should not be shared

🔘 Quick interface:
Having all features reachable without switching screens

🧠 Use of translation memories:
Translate with previous translation memories to ensure consistency

User story
“As the an expert translation Manager, i want to be able to translate texts with the company’s translation memories on the suite where im producing/reading my content, so i can save time when on my daily tasks without compromising the quality and security of my data”.

6. Mapping user flows for feature development

I mapped a user flow to see all the features that need to be included in the product. After mapping out all the features, we went through and prioritized them with the client. This way, we ended up with the must-have set of features for the MVP (Minimum Viable Product).
User Flow for document translation

🖌️ Design

5. My shaping my ideas into visual solutions
The first step in my design process is creating low-fidelity sketches. While digital wireframes and visual design take days and weeks to complete, sketches can be done in a few hours, giving the team and me the option to explore different possibilities.
I also had to keep in mind the design constraints for designing an Add in for the Microsoft suite. The access points and location of the app were already predefined by Microsoft , I had do accommodate the existing UI of flow to their parameters
6. Evolving my visual solutions
The mid fidelity screens helped me to be aware of some functionalities that were not yet on the first sketches. These screens also helped me to understand which components from the design system would be useful to include to perform the tasks.
6. How to measure if it is a successful product?
With my product manager, we created together the metrics to track the success of the feature. These metrics were also gave us ideas to explore for new discovery processes of features.

app from the suite do you use the most?- Which

app from the suite do you use the most?- Which

app from the suite do you use the most?- Which

7. Handoff to development
I worked on the look and feel of the design based on the existing design system from the product that i had previously built. The design system is a library of the frequently used elements (called components) using the Atomic design process. This method allows designers to maintain consistency and cut down on development time by reusing components.

Once the designs were finished, developers could start implementing them. At this point, I prepare and export every design asset so that front-end developers have everything they need to start working. Having the design system in place, easily accessible for developers, is a massive time-saver.

Final designs

Lets Connect!

Whether you have a project in mind or just want to chat about design, reach out!