UI UX Portfolio in Sri Lanka: Write a Clear Case Study

A UI UX portfolio case study should explain a design decision, not just display finished screens. For a Sri Lankan applicant, a local service example can make the problem concrete, provided you distinguish real research from assumptions and practice work.

A fictional appointment service is a useful starting point: someone needs to find a suitable time, understand the service and confirm a booking.

Define the user problem

Write a short problem statement before opening a design tool. For example: “A first-time visitor needs to understand the service duration and available times before booking.”

List what you know, what you assume and what you need to test. Do not invent interviews or claim that users requested a feature when you have not spoken to them.

Explain your role, project duration and constraints. If the work is a personal exercise, label it clearly.

Design a small complete journey

Map the steps from arrival to confirmation, including errors and empty states.

The W3C forms tutorial is a primary reference for accessible form design, including labels, instructions and feedback. Apply those principles to the actual journey rather than treating accessibility as a final decorative check.

Record why you changed the design

Show one early version and explain the uncertainty it was intended to test. Then describe what you observed and how the next version responds.

In a fictional exercise, a participant might overlook the service duration because it appears only after time selection. If you actually observe that behaviour, you can document moving duration information earlier and testing again.

If you have not run the test, describe it as a proposed test. An honest plan is more credible than fabricated research findings.

Run a focused usability session

Ask a participant to complete a task without explaining the interface in advance. Observe where they hesitate, what they misunderstand and whether they reach the intended result.

Use appropriate consent and avoid collecting unnecessary personal information. A small convenience sample can reveal usability problems, but it does not represent every Sri Lankan user.

Record the device, language and task context. A design that works on your large monitor may be difficult on a small phone or with longer translated text.

Write the case study as a decision trail

Include the problem, constraints, research method, selected findings, design changes and remaining limitations. Use readable screenshots with a short explanation of what matters.

Avoid presenting every sketch you created. Choose the evidence that helps a reviewer understand the decision.

Finish with the next question you would test. If the prototype has not been implemented, do not claim improvements to real conversion rates or business revenue.

Do you need a real client?

No. A clearly labelled personal project can demonstrate useful design thinking. Do not invent a client endorsement.

Should you include only the final screens?

Show enough process to explain the result. A few well-chosen comparisons are more useful than a long gallery without reasoning.

Can AI generate the interface?

It can help explore alternatives, but you remain responsible for the requirements, evaluation and explanation. Identify your actual contribution.

What makes the case study local?

Use a realistic context such as mobile access, language needs or a local service workflow. Avoid claiming that all Sri Lankan users behave the same way.

Related guides

• Career Change into IT in Sri Lanka: A 12-Week Plan
• IT Internship Applications in Sri Lanka: A Practical Plan
• LinkedIn Profile for IT Jobs in Sri Lanka: Examples

Browse the Sri Lanka work and technology guides for more practical application, AI and workplace projects.