The clumsy checkout you quietly rebuilt, the Figma file no one outside the team ever sees, the ten-second reason a button moved three pixels — each one is a carousel or a Reel that shows how you think long before anyone reads your résumé. Here is how to put a season’s worth of them on one calendar, showing only work you have the right to show and crediting everyone who touched it.
@mimimichi
A portfolio framed around decisions, not just screens — take the structure, skip the guaranteed-hire promise.
Real video · @mimimichi on YouTube
If you design products for a living, your hardest marketing problem is not that the work is invisible — it is that the best parts of it are. The hours you spent untangling an information architecture, the five rejected button states, the user interview that changed everything: none of it survives in the shipped screen a recruiter glances at for six seconds. A hiring manager scrolling at night, a founder who just realized their app confuses people, a fellow designer deciding who to recommend for a contract — they are all forming an impression of you from fragments, and the designer who can show the thinking behind one clear decision is the one they screenshot and remember. The craft is already in your Figma files. The problem is that you are mid-sprint with a usability readout tomorrow, a handoff to annotate and a stakeholder waiting on a flow, and nobody opens Instagram at the exact minute a sharp little process story would land in the feed of someone deciding who to hire. That gap — between the work you have done and the moment you could show it — is what a schedule closes.
We have looked at a lot of designer marketing, and UX sits in a particular spot: the output is a screen anyone can screenshot, but the value is the reasoning nobody can see. A recruiter cannot tell from a clean dashboard whether you lucked into it or fought for every decision with research and rationale. On Instagram, a carousel that walks through why the checkout went from five steps to three is the closest thing to watching you work that a hiring manager will get before an interview — and it is why process, not polish, is the content that actually earns the follow and the DM.
So you are really serving two overlapping people. The first is the hiring manager or client who is quietly evaluating how you think — the startup founder whose onboarding is leaking users, the design lead filling a mid-level role, the agency owner sizing you up for a contract. Case-study carousels and before-and-after Reels that show one decision at a time prove your judgment in a way a static mockup never can. The second is the fellow designer and the wider community who follow for the craft and quietly become your referral network; they amplify the work that shows real thinking and skip the work that only shows taste. For both, your bio link to a real portfolio and a dependable posting habit are what turn a scroll into a lead.
The non-negotiable running underneath all of it is permission and honesty. Show only work you have the right to show: client and employer projects are often under NDA, and unreleased products stay confidential until the company says otherwise — when in doubt, ask, or rebuild the idea as a clearly labelled personal concept. Credit every collaborator by name and never present a team’s work, or a redesign you did on spec, as something you shipped alone or that went live when it did not. Do not invent testimonials or metrics. Done that way, Instagram becomes the most efficient portfolio a designer has, and a reliable scheduler is what lets one batched afternoon show up as a steady, credible presence all week.
A fictional but realistic UX-designer Instagram profile, before and after applying our recommendations
BEFORE → AFTER
@jordan_makes_stuff
Designer. I make things look nice. DM for work.
19 posts · 380 followers · no portfolio link, no focus, scattered mockups
@jordan.designs.ux
Product & UX designer · redesign breakdowns & process, decision by decision · own work, collaborators credited · portfolio ↓
120 posts · engaged designer & recruiter following · portfolio link in bio
mimi michi — a channel on UX careers, portfolios and the honest reality of breaking into product design
REAL CASE STUDY
Judging by its title — “The UX portfolio that got me HIRED” — this video leans on a confident outcome in the headline, and that is exactly where we want to be careful: the lesson worth taking is not the guarantee the title implies, because no portfolio reliably ‘gets you hired’ and no honest designer should promise a recruiter or client a specific outcome. The transferable idea is quieter and real — that a portfolio framed around clear decisions and visible thinking is far more persuasive than a gallery of polished screens, and that showing the reasoning is what moves a hiring manager. For a UX or product designer the takeaway is the mechanism, not the promise: structure each piece around the problem, the decision and the result, credit the people you worked with, and show only what you have the right to show. We would ignore any implication of a guaranteed hire and keep every post honest about scope and ownership. We have not watched every second, so treat our read as an informed inference from how the video presents itself rather than a frame-by-frame verdict.
Steal this: Commit to one decision-led case-study carousel and one honest process peek every week and let them compound — and never attach a guaranteed outcome, shipped claim or uncredited teammate to any of it.
Lead with the before-and-after, because contrast is the thing a non-designer can feel instantly. The format that works hardest is the redesign carousel: slide one shows the cluttered original, the middle slides isolate one decision each — why you cut a field, why you grouped these actions, why the empty state changed — and the last slide shows the calmer result. Keep the scope honest: if it is a self-initiated redesign of an app you do not work on, say so, and never imply the company shipped your version. We would schedule two or three of these a week, rotated across project types so the feed shows range rather than one trick.
Then show the messy middle, because that is where your judgment lives. A short Reel of a Figma file zooming through twelve rejected button states, a thirty-second “the one usability finding that killed my favorite idea,” a time-lapse of a wireframe becoming a flow — process peeks like these are the hardest thing for a weaker designer to fake and the most persuasive thing a strong one can post. When the work is a real client or employer project, show it only with permission, blur anything sensitive, keep unreleased features off-screen, and credit the researchers, engineers and fellow designers who shaped it. Pretending a group effort was a solo one is the fastest way to lose the respect of the exact community that refers work.
Round it out with the human and the useful: a quick design-tip Reel, a “day in the life of a product designer,” an honest take on a tool or a pattern, a peek at how you run a critique. These build the personal brand that makes a recruiter feel they already know you. Keep the whole mix — your short-form teardowns included — on one calendar so you can see the balance of show-the-work, show-the-thinking and show-the-person at a glance.
Mike Locke’s “My Thoughts on Personal Branding & Portfolio Websites — UI/UX Design” is the kind of practitioner-to-practitioner perspective we’d point a designer toward — a working UI/UX designer arguing that your personal brand and the work you choose to show are a deliberate, owned thing, which is exactly the mindset a content calendar is meant to enforce. @MikeLocke on YouTube
Here is where a lot of designers quietly waste effort: they measure a portfolio carousel the way a lifestyle account measures a reel, chasing likes and feeling flat. Likes do not book interviews. The metrics that matter for a designer building toward work are the ones nearest a decision — saves, shares, profile visits, bio-link taps to your portfolio, and the DMs that open with “are you open to contract work?” or “we’re hiring, is this your portfolio?” Watch those first and treat raw reach as a weak signal, useful mainly for learning which kind of case study pulls the people you want.
Saves and shares deserve real weight here, and for a reason specific to this field. When a hiring manager saves your redesign carousel, they are filing it against a role they are trying to fill; when another designer shares it, someone whose taste the industry trusts has just vouched for your thinking — which is how referral-driven design hiring actually works. A steady climb in profile visits and bio-link taps tells you the work is doing its real job of sending qualified people to your portfolio. Comments are a signal and a responsibility at once: engage generously, credit anyone who asks who else worked on a project, and if someone requests the file or the full case study, send them to your portfolio rather than dumping client assets into a public thread.
The practical move is to review everything in one place each week, tag which posts preceded a real inquiry or a spike in portfolio taps, and feed that back into the next calendar. If your before-and-after carousels drive the interviews while your tool-tip Reels build the slower following, you weight the calendar toward case studies when you are actively job-hunting or opening contract slots. A scheduler with built-in analytics closes that loop in one view; if you want the broader framework, our social media scheduler guide walks through it step by step.
Three steps, one Figma file, no NDA leaks
QUICK START
SocialBlaze helps you plan, write, and publish across every platform — free to start.
A workable week for a UX designer assumes you are buried in a sprint and nobody is posting live between critiques and handoffs. Everything here is batched and scheduled in one sitting. We anchor the week on Tuesday and Wednesday, when recruiters and design leads are in work mode and most receptive to a sharp case study, and we keep the mix balanced so the feed shows the work, the thinking and the person across the week.
A repeatable seven-day framework you can start using tomorrow
SAMPLE CALENDAR
Spend this week turning finished work into a bank of show-ready pieces rather than scrambling for ideas later. List the projects you actually have the right to show — self-initiated redesigns, personal concepts, and any client or employer work you have explicit permission to share — and for each, pull out the two or three decisions worth a carousel. Where a project is under NDA or the product is unreleased, either rebuild the idea as a clearly labelled personal concept or leave it out; do not gamble with confidentiality to pad a feed. Set the profile up properly too: a bio that names what you do and who you help, an accurate portfolio link, and a clear note that you show your own work and credit collaborators. By the end of the week you should have a dozen decision breakdowns banked and a profile that reads as thoughtful, specific and honest. The goal is not virality — it is never again staring at an empty calendar while a sprint swallows your evenings.
Now you publish on schedule and watch what happens. Keep the Friday hero case study sacred and fill the rest from your growing library. Reply to every comment and DM quickly, and hold a simple line: when someone asks who else worked on a project, credit them plainly, and when someone asks for the full file or a client asset, send them to your portfolio rather than posting confidential material in a public thread. Start noting which posts draw real inquiries versus which just draw applause — a “we’re hiring, is this your work?” is a signal, a fire emoji is not. Keep ownership honest in everything you publish: never imply a spec redesign shipped, never present a team effort as solo, and never invent a metric to make a result sound bigger. Repeatable, careful and consistent beats clever here.
Three weeks in, patterns appear. Maybe your before-and-after redesigns drive the actual portfolio taps while your tool tips build the slower community following. Maybe mobile app work pulls startup founders while your design-systems content pulls enterprise recruiters. Rebalance the calendar toward whatever precedes real inquiries and move pure-applause content into supporting slots. This is also the week to deepen a couple of your strongest pieces into full written case studies on your portfolio, so the Instagram carousel is the teaser and the link is the payoff. Keep every expansion honest about scope and permission — a richer case study is also a bigger confidentiality surface, so re-check what you are allowed to show before you publish more detail, and keep crediting the people who shaped the work.
By now the loop should feel automatic: batch-build carousels and Reels on a quiet afternoon, schedule the week or month, review the numbers on Monday. Formalize it. Keep a running list of decisions worth showing so you never run dry — every project you finish is several posts — and build a simple template: before, decision, after, credit, link. Set a recurring calendar block for batching and queue your strongest case studies for the weeks you know you will be slammed, because a punishing sprint is exactly when you have zero time to post live but most want your name in front of people who hire. The aim is a portfolio engine that runs on the work you are already doing and an hour of scheduling, not on you finding spare energy after a ten-hour day in Figma — and one that stays honest about ownership, respectful of every NDA, and generous with credit at every step, because in this field your reputation among other designers is the whole asset.
Only with permission, and only within whatever agreement you signed. A great deal of UX work is covered by an NDA or belongs to an employer, and unreleased products are confidential until the company decides to announce them — posting a leak can cost you the relationship and the reference, and sometimes more. The safe path is to ask explicitly before you share anything client-related, and to get a clear yes about which screens, which details and which timing are okay. When you cannot get permission, you still have options: rebuild the idea as a clearly labelled personal concept, show a generic version of the pattern rather than the actual product, or focus on process and principles that do not expose anything confidential. Whatever you post, credit the researchers, engineers and designers who worked on it, and never imply a concept shipped if it did not. Protecting confidentiality is not a limit on your content; it is part of what makes you someone a company trusts with real work.
Three to five times a week is the sweet spot for most designers. That is frequent enough to stay visible to recruiters and the design community without burning out your supply of showable work or pulling you away from the actual job. Consistency beats volume every time: four scheduled posts that reliably go out each week do far more than a burst of a dozen followed by three silent weeks because a deadline hit. Since every finished project is several decision breakdowns and your process generates material constantly, hitting three to five is realistic once building a carousel becomes routine. Batch the whole week in one sitting and let the scheduler publish at sensible times, so a brutal sprint never knocks you off rhythm exactly when you most want your work seen.
This is the exact problem scheduling solves. You are not going to stop mid-sprint to craft a caption and build a carousel, and you should not try. Instead, batch your posts in a calmer stretch — a weekend or a quiet week between projects — turning finished work into a queue of decision breakdowns, then spend one hour loading a full month into a calendar. From there it publishes itself at sensible times while you keep your head down on the deadline. The labor shifts from “post daily” to “build ahead and batch,” which actually fits how design work flows between intense sprints and quieter gaps. The weeks you are most buried are the weeks a visible portfolio matters most, especially if you are quietly open to your next role, so build the queue before the crunch hits.
Be specific about your own contribution and generous about everyone else’s. Most product work is a team effort — researchers, engineers, PMs and other designers all shape the outcome — and the designers other people respect are the ones who say plainly “I led the flow and interaction design; research was by X, and Y built it.” Name your collaborators, and if you are posting a shared project, it is good practice to let them know and tag them. Never present a group effort as solo, and never claim a decision that was not yours. This matters beyond ethics: the design community is small and well-connected, and a reputation for overclaiming travels fast, while a reputation for crediting people fairly is exactly what makes other designers want to work with you and refer you. Honest attribution is not modesty; it is how trust compounds in this field.
Show your thinking and your craft, never a guaranteed outcome. It is tempting to caption a redesign with “this will double your conversions” or “guaranteed to fix your retention,” but a design’s impact depends on the whole product, the market and the team, and promising a specific business result you cannot control is both dishonest and easy to disprove. Present a self-initiated redesign as your concept, not as something the company adopted; share real metrics only when you have permission and they are genuinely yours to share; and never fabricate a testimonial or a number to make a case study hit harder. Frame everything as “here is the problem I saw and the decision I made” plus a calm invitation to see the full work. The designers who represent their work accurately attract the clients and teams who stay, and in a small, reference-driven field those relationships — and the referrals they generate — are what actually compounds, far more than any viral claim.
You are already doing the work that makes a portfolio — the only missing piece is a place to plan the posts and a way to publish them without stopping mid-sprint to do so. Load a week of case-study carousels, process peeks and honest design tips into SocialBlaze on a quiet afternoon and let it carry your name across Instagram and your other networks while you stay heads-down in Figma, every post showing only what is yours to show and every collaborator credited.
Case-study videos are embedded from their creators’ public accounts and remain the property of their creators. Figures mentioned reflect publicly visible information at the time of publication (October 2026). SocialBlaze is an organic social media management tool — it does not run ads or manage paid campaigns.