Why I Teach Design as a Ladder, Not a Menu: Inside My Six Courses at IOP Digital

I teach six design courses at IOP Digital, and none of them were built to stand alone. Seeing First teaches a beginner to read a layout before touching a tool. Brand Gravity and Four Seconds teach the two halves of a first impression, what a stranger believes before they've used the product and what they decide once they have. Prompt to Pixel teaches where AI belongs in that process and where it doesn't. Brand-to-URL and Decision Entropy close the gap between a Figma file and a shipped, defensible piece of work. I built the sequence this way because I kept watching designers learn software before they learned to see, and it shows up later as work that looks finished but doesn't hold up under a real client's questions.

I studied physics before I studied design, and six years and 150-plus projects later, that's still the lens I actually work through. Physics trains you to look for the invisible force behind a visible result: the thing you can't see directly but can prove is there because of what it does to everything around it. A falling object tells you about gravity without gravity ever showing up in the photo. A product tells you about trust the same way. Nobody writes "I don't trust this" in a support ticket. They just leave, and the drop-off curve is the proof.

That habit is why I don't teach branding as decoration or UI as polish. My branding work starts with positioning, deciding what a stranger has to believe in the first four seconds before I draw a single logo mark. My product work starts with effort, finding every step that adds doubt and cutting it, and finding every step that builds trust and keeping it. I teach the same way I work. See first, then learn the tools, which is also the name of the first course for a reason.

Seeing First is twelve weeks and it opens with two weeks of no software at all. Students annotate ten real screens, marking exactly where the eye lands first and why, before they open Figma. Then they move through grids, typography, colour, and three tools, Figma, Photoshop, and Illustrator, redesigning real screens and defending every change in writing. I made it the entry point on purpose. A student who can explain why their eye goes to one button before another will make better decisions in every course that follows, and a student who skips that and goes straight to tools usually produces work that looks fine and explains nothing.

Brand Gravity and Four Seconds come out of the same four-second idea in my own practice, applied to two different layers of the same product. Brand Gravity is the layer before someone opens the product at all: positioning, naming, a logo system, a full guidelines document, the pull a brand exerts on a stranger before a single screen loads. Four Seconds is the layer after that, inside the actual interface: flows, wireframes, cognitive load, Hick's Law, usability testing with five real users. A brand can earn someone's attention in the first four seconds and then lose their trust in the next four, on the signup form. I've watched that exact sequence happen in client audits more times than I can count, and it's the reason these two courses exist as a pair rather than one combined class.

“

A logo tells people what you want them to believe. The interface tells them whether it's true.

Prompt to Pixel is the course I get the most skeptical questions about, usually some version of "is this just teaching people to prompt their way through design." It isn't. Twelve weeks, and the first deliverable is a prompt library of ten tested prompts with notes on where each one failed, because the failure notes matter more than the successes. Students use AI for research synthesis, image generation, and even a coded prototype through Cursor AI, but every week ends with the same question: where was the AI output wrong, and who caught it. I don't think AI replaces design judgment. I think it removes the excuse for not having any, because the tool will happily ship your bad decision at ten times the speed if you let it.

Brand-to-URL exists because I kept seeing the handoff gap between a beautiful Figma file and a site that actually works in production, and I kept seeing it get blamed on developers when the real problem started upstream. Twenty weeks, one person owns the whole chain: art direction in Figma, a working prototype in Figma Make, a coded build in Cursor AI, a Lighthouse performance target of 90 or higher, and a launch on a real domain with a working contact form. No handoff, because the handoff is usually where the brand promise and the shipped product quietly stop agreeing with each other.

Decision Entropy is the capstone, twenty-four weeks, and it's the course where I finally say out loud what the other five have been building toward. Every unnecessary component in a product raises the uncertainty a user feels, even when they can't name why. Students audit a live product specifically for decision entropy, trust friction, and perception gaps, then build a full design system, write a published case study, and learn to scope and price client work. This is also where the physics habit comes back around. A system with fewer unnecessary states is more stable, in physics and in a dashboard. The advanced work isn't adding more capability. It's finding what to remove.

If you're deciding where to start, don't start with the course that sounds most impressive. Start with the gap you actually have. If you've never designed anything and the idea of a 12-column grid means nothing to you, that's Seeing First, full stop. If you can already use Figma but every interface you ship feels like it's missing something you can't name, that's Four Seconds. If you can design but you've never built a brand from positioning through guidelines, that's Brand Gravity. Decision Entropy only makes sense once you already have a portfolio with real shipped work behind it, which is exactly why it's the one course on the ladder that asks for a prerequisite.

I run IOP Academy because I kept doing this for free informally before it had a name attached to it, critiquing portfolios for friends, explaining why a particular layout wasn't working, and realizing the explanation was always more valuable to the person than the fix itself. Pakalign Studio is where I do the client work that keeps the teaching honest. Every case study I bring into Decision Entropy, every example I show in a Brand Gravity critique, comes from a real project with a real client attached, not a hypothetical.

Two things I hear back from former students stick with me more than the testimonials page does. One student described going from making things that looked good to making things that worked as experiences, and said the portfolio from the program got her interviews everywhere she applied. Another described the structure itself as the thing that changed how they approached modern digital work, more than any single tool or technique taught inside it. Neither of those comments is about software. They're both about the shift from decorating a screen to defending a decision, which is the actual thing I'm trying to teach underneath all six course titles.

None of this means the ladder is the only valid path into design, and I'd be overselling it if I said otherwise. Some of the strongest designers I know never took a structured course at all, and some students finish Seeing First and still need another year of unglamorous repetition before client work gets easy. What the sequence does is remove the guesswork about order. You don't have to figure out on your own whether to learn brand or interface first, whether AI belongs in week one or week twelve, or whether you're ready for a capstone. I already made those calls, based on what actually breaks when designers skip steps.

I get asked sometimes whether six courses is too many, whether it would be simpler to collapse this into one long program. It probably would be simpler. It wouldn't be honest. Brand work and interface work and production work are different skills with different failure modes, and a student who's strong at one is often weak at another in ways that don't show up until a real client is involved. Teaching them as one blurred course would hide exactly the gap I built this ladder to find.