How can you document and communicate interface testing results in a portfolio?

Just to add to this, if a portfolio requires any password, then the password should be easily accessible on request. Learning through experience.

In my experience so far, websites work as one of the best formats for portfolio. If you host that on a domain that matches your name, then it will look even more premium and professional. Other than that, a pdf could be a good format as well.

Documentando Testes de Interface no Portfólio: 1.Introdu??o Contexto, objetivo e desafios do projeto. 2.Objetivos dos Testes Defina claramente os objetivos dos testes de interface. 3.Metodologia Descreva brevemente a abordagem e ferramentas utilizadas. 4.Cenários de Teste Destaque as tarefas-chave e cenários testados. 5.Ferramentas Mencione as ferramentas específicas empregadas. 6.Resultados Apresente insights com gráficos e capturas de tela. 7.Conclus?es Analise os resultados e destaque conclus?es principais. 8.Aprendizados Compartilhe insights e recomenda??es. 9.Feedback dos Participantes Inclua cita??es ou feedback direto dos participantes. Isso vai ajudar rs

Eu considero o site como a melhor experiência para se contar uma história. Ultimamente as plataformas de sites est?o cada vez mais acessíveis para arrastar blocos de conteúdo. Sendo assim, você tem o seu menu para inserir seus links, seu visual, suas redes sociais e contatos. Claro, dá um pouco de trabalho. Mas n?o é isso que as empresas est?o procurando nos seniores? Profissionais que encaram desafios para oferecer a melhor experiência?

Penser le portfolio au regard de votre stratégie de diffusion : avez-vous déjà un site ? un CV ? un linkedIn ? êtes-vous déjà en contact avec l'entreprise où vous postulez ? Vous adressez-vous à quelqu'un des RH ou des designers ?

Never show only the final mockups. Show the problem to resolve, show the process. How you do solved the problem? Show that!! :D

In addition to the ideas already mentioned, when available, select a project that had a direct business impact. Using quantitative data that connects to business results or had a commercial impact demonstrates the value your work has to an organization.

Try to match the project: - to the position - domain of business - to demonstrate the most relevant skill as shown in the JD

Es importante seleccionar los mejores proyectos que hayas realizado (con 3 o 5 máximo basta). Recuerda que además de mostrar el mockup, es importante incluir un poco del proceso previo para que puedan conocer que metodologías utilizas y tu estilo de trabajo

Include projects that you think are one of your biggest projects and will appeal to your target audience the most. Also, try to avoid projects that you made while watching a course because your client/recruiter might already be familiar with the fact that this exact project was shown in a course and he might think that it is copied from there.

There are several ways to structure. Easiest would be: 1. Problem 2. Process 3. Solution 4. Business/User impact. This is the easiest that you can scale up & down. Present as you speak also.

A good structure is: - Intro to the project - Problem statement - Team structure - Your role and contribution - Methods - Results (Summary of findings) - Outcomes (What was the impact of your project?) - Deliverables (Link to what you're willing to show, e.g. testing plans, session guides, reports) - Retrospective (what worked, didn't, and what you'd change)

I agree. STAR(Situation, Task, Action, and Result) method could be very efficient from a physiological point of view. Also, try to mention your main projects at the top because many times, clients view only one or two projects from your portfolio, especially when they are extremely busy.

Usualmente, una buena lectura de un caso de estudio suele funcionar de la siguiente manera: - Overview del proyecto - Tu rol y responsabilidades - Descripción del problema a resolver - Metodología utilizada - Actividades y resultados Esta es una estructura básica que funciona para la mayoría de los casos, sin embargo, el contexto de cada proyecto/producto puede variar en función de lo que se desea presentar.

Gardez en tête que votre recruteur est un expert comme vous. Dans vos projets, ne perdez donc pas de temps à expliquer les méthodes et leur fonctionnement. Citez-les simplement et expliquez plut?t pourquoi et comment vous les avez mis en place ainsi que les grands enseignements que vous en avez tiré. Pour que votre recruteur adhère à votre démarche, il doit pouvoir suivre votre cheminement de pensé et s'appuyer sur les éléments que vous avez récoltés.

Our memory is more used to visuals and components than to reading text. Keeping this in mind , we shouldn't forget that we have to know what the limit is, just portraying everything in graphics and impressions can also be overwhelming and misunderstood so the right balance is always appreciated much more than just focussing on one.

Je pense que montrer des avant / après des écrans est un premier point pour illustrer les changements effectués. Bien s?r il faut accompagner ces mockups : point de douleur identifié, objectif visé, méthode utilisée, conclusion de l'analyse des résultats, et si possible les métriques avant / après qui prouvent l'amélioration voire l'atteinte de l'objectif le cas échéant.

Adding screenshots of Tableau or Mixpanel tracking metrics helps to explain what happened, e.g., succeeded or failed, what you learned and how you pivoted.

Most people understand the easiest when they can see something. Visuals are extremely important. Image is so much easier to communicate information with. There is almost no effort required to understand images. I tend to annotate screens that I tested with users quotes.

Es importante destacar la muestra (personas) de la prueba y las funciones evaluadas en un resumen que sea entendible para la mayoría. Muchos de nosotros tendemos a ser visuales, por lo que apoyarte de la captura o mockup al que hace referencia siempre ayudará, adicionalmente utilizar un mapa de calor dará énfasis en elementos a destacar de la interfaz y por último trata de utilizar "quotes" de los mismos usuarios para dar visibilidad de puntos de mejora o puntos bien trabajados

Pour cette étape, des notions d'UX Writing vous seront d'une grande aide. Pour ceux qui ne sont pas à l'aise avec les mots, vous pouvez rédiger une intention et demander à ChatGPT de l'améliorer. Gardez en tête que votre recruteur ne peut pas consacrer sa journée à lire des portfolio. Il est dont important d'aller à l'essentiel et de garder des informations bonus que vous pourrez transmettre lors de votre entretien.

User experience testing is crucial. Using common language, rather than specialized terms, enhances accessibility and comprehension for a broader audience.

Kepping the sentences short, and the trains of thought structured as a cause and effect relationship. Even just these two points help build a better, more easy-to-understand narrative for your UX research portfolio.

Try to write everything in a very simple language and try to avoid technical abbreviations as your client might not be familiar with the term.

In summary, for an effective portfolio, use clear and concise language, avoid jargon, and opt for direct communication of interface testing results. Employ active voice, short sentences, and bullet points for readability. Organize content with transitions, headings, and subheadings. Maintain a consistent and professional tone and style throughout the portfolio.

My perception is that connecting with random people on social platforms who presently work or learn UX. This will get the unbiased feedback at the same time we get connections of different mindsets to share our thoughts and to become better of us.

I personally follow 2 steps in taking in feedback, first going and interacting with people who are somewhat related to the industry cuz this allows us to understand critical thoughts of other designers or developers and next going to non tech people and getting a know on what a normal non background person would interpret once they wish to go through the project.

It is important to ask the right people for the feedback who have worked in the area you are looking to improve and have delivered in that area. There are multiple self declared "Experts" in the market. Once you receive the feedback, spend some time to think over it and process it before you act on the feedback.

Results aren't as important as the process you went through to select your methodology, how you conducted the study, and the impact of what you learned on the team and the product. A general format to follow: What was the research question/design challenge/business opportunity you were seeking to inform? What method did you choose and why? What other methods did you consider? What were the constraints that came up for you as you were designing your study? What was the impact? What changed in the product and in how the team approached similar questions that followed? And finally, what would you have done differently in the future if you were to do this again?

You can use user journey maps to illustrate the impact of your interface testing. Show the user's experience before and after the testing, highlighting pain points that were addressed and improvements that were made. This storytelling through user journey’s narrative approach can make your portfolio more engaging and easy to understand.

Always update your portfolio with new projects and work that you do. It shows that you are using updated methodologies and technologies. It also shows that you are working on new projects all the time. One more thing I want to mention is something that people ask me a lot. How many projects should you have in your portfolio. While there is no upper limit, as more projects show that you are more experienced, you want to make sure that you have at least 2 or 3 projects to give a good impression.

A portfolio is not the location for in deep description of methodology. I sometimes get links to very long and complex portfolios and to be honest, I do not have time to read the carefully. For me in a hiring situation I look for why someone chose to do what, what came out of it and what was actions taken preferably as short bullet points I then look into if I believe it was the best options given the circumstanses. I am aware this might reflect unfair sometones but hey I believe I am not the only one not having enough time for in deep portfolio reading.

Beyond the hard facts and the inclusion of your thought process, constructing a good narrative is crucial when showcasing interface test results. It's not just about laying out the situation and the task; it's about telling the story behind the challenges, bringing out the emotions, and emphasizing the impact on users. For instance, including user anecdotes, highlighting their experiences and frustrations, adds an emotional layer to the narrative. This doesn't just make the test results more understandable, but also ensures they stick in the minds of your audience.