Learning design often gets stuck between two bad habits. You spend months taking courses without showing anyone what you can do, or you start posting work before you have enough structure to know what you are actually trying to improve.
This 90-day plan is for designers who want to build skills and a portfolio at the same time. It works especially well for students, junior designers, career switchers, and designers returning to active practice. The idea is not to publish every random exercise. It is to create a visible record of what you studied, what you made, what went wrong, and how your thinking changed.
The plan uses a weekly rhythm: learn something, apply it to a small design problem, document the process, publish the result, then use feedback to decide what to practise next. That approach turns the portfolio into evidence of your design process, not just a collection of polished screens.
Why Learning in Public Works Better Than Private Practice
A designer can spend weeks watching tutorials and still struggle when facing a blank Figma file. The problem is rarely a lack of information. It is the gap between understanding a concept and making decisions with it.
Learning in public closes that gap because every week has an output. You are forced to move from passive learning to visible practice.
Treat every week as a small design project
Instead of setting a vague goal such as “improve my UX skills,” give each week a specific problem.
For example:
- Week 1: Redesign a confusing mobile sign-up flow.
- Week 2: Practise information hierarchy on a dashboard.
- Week 3: Study typography and rebuild one landing-page section.
- Week 4: Conduct five usability observations on your prototype.
- Week 5: Improve the previous project using what you learned.
The project does not need to be original in the business sense. A familiar product can be useful because you already understand enough of the context to concentrate on the design problem.
The important part is the decision-making. Why did you remove a field? Why did you change the hierarchy? Why does one button receive more visual weight? Why does the user see this information before another piece of information?
Those decisions become portfolio material.
Publish the thinking, not only the final screen
A polished mockup tells people what you produced. It does not necessarily tell them whether you understand design.
When you publish a project, show some of the reasoning behind it:
- What was the problem?
- Who was affected by it?
- What did you observe or research?
- What alternatives did you consider?
- What changed during the process?
- What would you test next?
This is particularly useful for UX portfolios because UX work is rarely judged only by visual finish.
A simple before-and-after comparison can sometimes communicate more than ten final screens.
Build a feedback loop
Public learning is not the same as posting constantly.
The useful loop is:
Learn → Make → Share → Receive feedback → Reflect → Make again
If someone points out that your navigation structure is confusing, do not immediately defend it. Ask what caused the confusion. If several people make the same observation, test the design again.
This creates something valuable over 90 days: a visible history of improvement.
The First 30 Days: Build Your Design Practice
The first month should be about consistency rather than trying to look senior. Your goal is to establish a repeatable design habit and create enough work to identify your strengths and weaknesses.
Weeks 1 and 2: Find your baseline
Start with an honest assessment of your current skills.
For a UX designer, examine areas such as:
- User research
- Information architecture
- User flows
- Wireframing
- Interaction design
- Visual hierarchy
- Typography
- Responsive design
- Accessibility
- Prototyping
- Usability testing
- Design systems
Do not rate yourself based on how familiar a topic sounds. Use a practical test.
For example, if you think you understand information architecture, take a real website with poor navigation and restructure it. If the resulting hierarchy is difficult to explain, that is a useful learning signal.
Your first public project can document the baseline.
Write something as simple as: “I am spending the next 90 days improving my UX process. This is my starting point.”
That honesty gives your future posts context.
Week 3: Rebuild instead of inventing
Choose an existing interface and recreate one small part of it.
Pick something such as:
- A checkout screen
- A banking dashboard
- A food-ordering flow
- A travel booking screen
- A SaaS onboarding sequence
Do not copy it simply to create another visual imitation. Analyse it.
Look at spacing, hierarchy, interaction states, error handling, content structure and responsive behaviour.
Then create your own version and explain what you would change.
This exercise is useful because removing the pressure to invent a complete product lets you concentrate on execution.
Week 4: Publish your first case study
Turn one of the first three weeks’ projects into a small case study.
Keep it compact.
Recommended structure:
- Problem
- Context
- Research or assumptions
- Initial flow
- Wireframes
- Design decisions
- Final screens
- What changed
- What you learned
- What you would test next
Do not fabricate research results to make the case study look professional. If you did not interview users, say that the project is a concept and identify your assumptions.
That distinction matters for credibility.
Google’s guidance continues to emphasise useful, original content created for people rather than pages produced mainly to manipulate Search.
Days 31 to 60: Move From Practice to Real Problems
The second month is where your work should become more realistic. You have already established a publishing habit. Now start working with constraints, incomplete information and feedback.
Weeks 5 and 6: Solve a complete user flow
Stop designing isolated screens.
Choose one task and design the complete journey.
For example:
Food delivery
Home → Search → Restaurant → Product → Cart → Address → Payment → Order confirmation
Or:
SaaS onboarding
Landing page → Sign-up → Account setup → Preferences → Dashboard → First action
Map the flow before opening your design tool.
This forces you to think about states and transitions rather than individual screens.
Ask:
- What happens when the user makes a mistake?
- What happens when there is no data?
- What happens when loading takes time?
- What happens when the user leaves halfway?
- What happens after the primary action?
- What information does the user need at each step?
These details are where interface design starts becoming UX design.
Weeks 7 and 8: Introduce real feedback
Now put your work in front of people.
You do not need a formal usability laboratory. Five relevant people can reveal surprisingly useful problems if you ask good questions.
Give them a task rather than explaining your interface.
Instead of saying:
“Click here to find your order.”
Say:
“Imagine you placed an order yesterday and want to check its current status. Show me what you would do.”
Then observe.
Do not immediately explain what the interface was supposed to mean.
Record:
- Where they hesitate
- What they click first
- What they misunderstand
- What they expect to happen
- Where they stop
- Questions they ask
The goal is not to prove that your design works. The goal is to discover where it does not work.
Use feedback to create version two
A strong learning-in-public post can show the change between versions.
For example:
Version 1: Users overlooked the secondary action.
Observation: Four out of five testers looked at the primary button first and ignored the supporting action.
Change: Reworked hierarchy and moved the supporting action closer to the relevant content.
Version 2: Tested again with a new set of users.
This is far more useful than simply publishing “Here is my new dashboard design.”
It demonstrates a design process.
It also creates evidence that your portfolio is based on decisions and iteration rather than decoration.
Days 61 to 90: Turn Your Practice Into a Portfolio
The final month is about selection and presentation. By this point, you may have ten or more small exercises, but you should not automatically put all of them in your portfolio.
More work does not always create a stronger portfolio.
Weeks 9 and 10: Identify your strongest work
Review everything you created during the first 60 days.
Score each project privately against practical criteria:
| Criterion | Question |
|---|---|
| Problem | Is the problem clear? |
| Process | Can I explain how I approached it? |
| Decisions | Did I make meaningful design choices? |
| Evidence | Did I use research, testing or clear assumptions? |
| Iteration | Did the design change based on something? |
| Visual quality | Is the final work professionally presented? |
| Learning | Can I explain what this project taught me? |
You are not trying to produce a perfect numerical evaluation. The purpose is to identify patterns.
You may discover that your visual work is strong but your research process is weak. Or perhaps your UX reasoning is good but your typography needs work.
That discovery should determine the next project.
Week 11: Build one deeper case study
Choose your strongest project and expand it.
This should be more detailed than your weekly posts.
A useful UX case study can contain:
- Project overview
- Problem statement
- User and business context
- Research or assumptions
- Competitive or comparative analysis
- User flow
- Information architecture
- Wireframes
- Iterations
- Final interface
- Prototype
- Testing
- Changes after testing
- Outcome or limitations
- Lessons learned
Do not add sections simply because other portfolios have them.
Every section should answer a question a reviewer might reasonably have.
If there was no client, no real product data and no usability study, state that clearly. A well-framed concept project is more credible than a fictional case study pretending to contain research that never happened.
Week 12: Build your portfolio around a point of view
Your portfolio should answer a simple question:
What kind of design problems do I want to be trusted with?
You might focus on:
- SaaS UX
- B2B dashboards
- Mobile applications
- E-commerce
- Healthcare UX
- Fintech
- Design systems
- Conversion-focused websites
- Product design
You do not need to lock yourself into one industry forever.
But if every project is unrelated, visitors have to work harder to understand your strengths.
Group projects around the type of problem you solve, not just the software you use.
“Figma Designer” says very little.
“UX designer focused on simplifying complex B2B workflows” communicates a direction.
Week 13: Publish the 90-day retrospective
The final week should not simply be another polished case study.
Publish what happened.
Talk about:
- What you expected to learn
- What you actually learned
- Which skill improved
- Which skill remained weak
- Which project received useful feedback
- What you changed because of that feedback
- What you would do differently
- What you plan to practise for the next 90 days
This gives your audience a reason to follow the next chapter.
It also creates a natural content series. Your portfolio becomes the destination, while your public learning becomes the story that brings people there.
Build a Simple Weekly System You Can Actually Maintain
A 90-day plan fails when every week becomes a large project. Your system needs to fit around work, studies or client commitments.
Use a five-part weekly cycle
A practical schedule can look like this:
Monday: Study one concept for 30 to 60 minutes.
Tuesday: Analyse an existing interface and identify how the concept is used.
Wednesday: Apply the concept to your own design problem.
Thursday: Refine the work and document important decisions.
Friday: Publish the result and ask one specific question.
Weekend: Review feedback and plan the next exercise.
You can compress this into fewer days if necessary. The sequence matters more than the calendar.
Keep a public learning log
Create one simple document with five fields:
What I learned
A short explanation of the concept.
What I made
A link or screenshot.
What changed
The most important design decision.
What feedback I received
Useful observations from other designers or users.
What I will practise next
One specific improvement.
After 90 days, this becomes raw material for case studies, social posts, portfolio updates and even job interviews.
Publish consistently without becoming a content creator
You do not need to turn design practice into a full-time social media job.
One useful post per week is enough to create a visible trail.
Good post topics include:
- “What I changed after testing this checkout flow”
- “Three problems I found in this onboarding screen”
- “I redesigned this dashboard without adding more features”
- “What I learned from rebuilding this mobile navigation”
- “Version 1 vs Version 2: what changed and why”
The content should come from the work.
Do not manufacture design exercises simply because you need something to post.
FAQs
Do I need to be an experienced designer before learning in public?
No. In fact, documenting your learning can be particularly useful early in your career. The important distinction is between presenting a learning exercise honestly and presenting yourself as an expert on something you have not yet tested.
What should I post as a beginner UX designer?
Post small, specific pieces of work: interface breakdowns, user flows, wireframes, redesign exercises, usability observations and lessons from iteration. A clear explanation of one design decision is often more useful than posting ten polished screens without context.
How many projects should a UX portfolio have?
There is no universal number that makes a portfolio effective. A smaller set of well-explained projects can communicate more than a large collection of unfinished exercises. Focus on showing different types of thinking, such as research, flows, interaction design, visual design and iteration.
Can I use redesign concepts in my portfolio?
Yes, but label them clearly as concept or self-initiated work. Explain what information you had, what assumptions you made and what you changed. Do not imply that you worked for the original company or that you achieved results you did not actually measure.
What if nobody gives feedback on my design posts?
Do not make public engagement your only feedback source. Ask specific designers, colleagues, classmates or users for targeted comments. Instead of “What do you think?”, ask, “Where does this flow feel unclear?” or “What would you expect to happen after this action?”
Is learning in public useful for getting freelance or design work?
It can help demonstrate your thinking, communication and consistency, but publishing alone does not guarantee clients or employment. Your strongest evidence still comes from relevant design work, a credible portfolio, clear communication and the ability to explain your decisions.
Conclusion
A useful 90-day design plan does not require three months of uninterrupted study. It requires a repeatable connection between learning and making.
Start with small problems. Study one concept, apply it, publish what you learned and use feedback to decide what comes next. During the first month, establish the habit. During the second, introduce real user feedback and more complete flows. During the third, turn the strongest work into focused case studies and a portfolio with a clear direction.
This approach works particularly well when you are building experience, changing careers or trying to move from visual execution toward stronger UX thinking. It is less useful if your only goal is to produce a large number of polished screens quickly.
The portfolio you have at the end of 90 days should not just say, “Here is what I can design.” It should give someone enough evidence to understand how you think, how you respond to feedback and how your work improves over time.