J
Ellis Empire · Content Studio
Batch 0 · Launching June 25, 2026 · Edmonton

The Standard,
Daily.

A content engine built to your voice · elevated, plainspoken, never selling. Three flagship posts launch this week, a seven-lane rhythm that never repeats, and a structured handoff your HQ agent can post on its own.

3
Flagships ready
4
Platforms each
7
Daily lanes
90
Day plan
110
Archive posts
00

The Voice, in one glance

The rules every word obeys · human or agent. Drawn straight from your Voice & Tone book, tuned to how you actually speak.

Open with · Good Day
Register · Elevated · visionary · warm
Never · Hype · shade · invented numbers
Money word · Investment, never price
Numbers · JetBrains Mono
Laugh · haha, never lol
CTA · None · let the work pull
Canvas · Near-black, one green
01

The Flagships

Three identity-defining pieces, posting today, Friday and Saturday. Each carries a full LinkedIn, Facebook, Instagram and TikTok version · tap through the tabs. The essay is the source; every platform version is native, not a copy.

The Opener · The Business of Trust · The Opener · 3 min · posts 2026-06-25

How I Talk You Out of Working With Me

The most useful thing a good advisor can say is no. So here is when you should not hire me.

Good Day. I want to begin our relationship the way I intend to continue it, by telling you the truth against my own interest. So here it is. Most of the people who contact me do not need everything they think they need, and a few of them do not need me at all. Part of my work, the part I am most proud of, is knowing the difference and saying so out loud.

This is not a humble brag dressed up as honesty. It is a method. A trusted advisor earns the title in the moments they decline the easy sale. If I will tell you to keep your money today, you can believe me on the day I tell you to spend it. Trust is built almost entirely in the places where I have nothing to gain.

So let me talk you out of a few things. If a simple template and an afternoon of your own care will serve the business you have today, take that road, and come back when you have outgrown it. If you want a new website because a competitor has one, that is vanity, not strategy, and vanity is the most expensive thing you can put on a balance sheet. If you want ten pages, you almost certainly need three. If you want everything at once, you need the one thing that moves the needle first, and the patience to let the rest wait until it earns its place.

I will also tell you when I am simply the wrong person. If what you need is a large team, many hands, many meetings, and a logo by Thursday, I am not your studio, and I will say so on the first call. I am one person who does the whole of the work, by choice. That is a gift for the owner who wants a single accountable mind, and a poor fit for the owner who wants a vendor to manage. Knowing which one you are is worth more to you than anything I could sell you.

There is a quiet economics to this that I have watched play out for twenty years. The businesses I talk out of the big thing today are the ones who return, unprompted, for the right thing later. They send their friends. They become the kind of client you build a whole practice around, because the relationship began with honesty instead of a pitch. Restraint is not me leaving money on the table. It is me choosing the longer, better table.

I think people can feel the difference immediately, even through a screen. There is a particular calm in being advised rather than sold to. The pressure leaves the room. You stop defending your budget and start describing your actual problem, and the moment you do that, we are already working well together, whether or not you ever hire me.

So consider this the most honest sales pitch you will read, which is to say it is not one. If you leave here having decided you do not need me yet, I will consider that a good outcome, and I will mean it. And if you leave thinking that a person who would talk you out of the work is exactly the person you want doing it, well. That is the quiet paradox this whole practice is built on, and you would not be the first to notice.

Either way, you now know how I will treat your money and your time, which is to say carefully, and as though they were my own. That is the entire offer. Everything else is just the work, and the work can wait until you genuinely need it.

Jonathan Ellis · Edmonton

The lead post. Counterintuitive, luxurious, supremely confident. Pairs with a single calm, composed brand frame. No selling.

I want to begin the way I intend to continue, by telling you the truth against my own interest.

Most people who contact me do not need everything they think they need. A few do not need me at all. Knowing the difference, and saying it out loud, is the part of my work I am most proud of.

A trusted advisor earns the title in the moments they decline the easy sale. If I will tell you to keep your money today, you can believe me on the day I tell you to spend it.

So I will talk you out of things. Ten pages when you need three. Everything at once when you need the one thing that moves the needle first. A website built on vanity rather than strategy. And I will tell you, on the first call, when I am simply the wrong fit.

Restraint is not leaving money on the table. It is choosing the longer, better table. If you decide you do not need me yet, I will consider that a good outcome, and I will mean it.

#design #branding #trust #Edmonton

Warm, neighbourly, disarming. The confidence reads as care, not bravado.

Good Day. Let me start the way I mean to go on, by telling you the truth even when it costs me.

Most people who reach out do not need everything they think they need, and a few do not need me at all. The part of my work I am proudest of is knowing the difference and saying so.

So I will happily talk you out of things. If a simple template serves the business you have today, take it, and come back when you have outgrown it. If you want ten pages, you probably need three. If you want a new site because a competitor got one, that is vanity, and vanity is expensive.

The owners I talk out of the big thing today are usually the ones who come back for the right thing later, and who send their friends. Honesty is just a slower, better way to build a business.

If you decide you do not need me yet, that is a good outcome, and I mean it. And if you decide that a person who would talk you out of the work is exactly who you want doing it, well, you would not be the first.

Confident and calm. The carousel is the whole argument; let it breathe.

Good Day. The most useful thing a good advisor can say is no.

Most people who contact me do not need everything they think they need. A few do not need me at all. Saying so is the part of my work I am most proud of.

Restraint is not leaving money on the table. It is choosing the longer, better table.

Carousel · 7 frames
1How I talk you out of working with me.
2Most people who contact me do not need everything they think they need.
3A trusted advisor earns the title in the moments they decline the easy sale.
4Ten pages when you need three. Everything at once when you need one thing first.
5If a simple template serves you today, take it. Come back when you outgrow it.
6Restraint is not leaving money on the table. It is choosing the longer, better table.
7If you decide you do not need me yet, that is a good outcome. And I mean it.
#design #branding #trust #Edmonton #yeg #smallbusiness

The confidence is the hook. Calm, warm, unhurried. Single take, direct to camera.

Length · 23s    Hook · Let me talk you out of working with me.
TimeVoiceoverOn-screenShot
0-4sLet me talk you out of working with me. I am serious.how I talk you out of working with meYou, direct to camera, calm, near-black room, one warm light.
4-11sMost people who contact me do not need everything they think they need. Some do not need me at all. And the part of my work I am proudest of is saying so out loud.·Hold on you, unhurried, steady.
11-18sIf a simple template serves the business you have today, take it. If you want ten pages, you probably need three. If you want a site because a competitor got one, that is vanity, and vanity is expensive.ten pages? you need three.Slight lean in, or a single composed object on the desk.
18-23sRestraint is not leaving money on the table. It is choosing the longer, better table. If you decide you do not need me yet, I will mean it when I say good.the longer, better tableBack to you. Let the last line settle in silence.
Audio · Quiet, confident, warm. No drop. The calm is the whole point.
Caption · The most honest sales pitch you will read, which is to say it is not one. Good Day from Edmonton.
Assets needed
  • · One calm, composed brand frame (dark, one green) for LinkedIn
  • · 7 carousel frames in brand tokens
  • · 23s single-take video, direct to camera
Flagship 01 · The Craft & Taste · The Essay · 3 min · posts 2026-06-26

Why Everything Looks the Same

The web is converging on a single template, and the machine is accelerating it. The only way out is judgment.

Good Day. There is a particular blue button I keep meeting. It sits beneath the same centred headline, above the same trio of feature cards, on a layout I have now seen ten thousand times. It is not that designers have stopped trying. It is that the tools have started deciding, and the tools have only one taste, which is the average of everything they were ever fed.

I have spent two decades in this work, and I have never watched convergence move this fast. A generation ago, sameness was a slow drift: everyone borrowed from the same handful of sources and eventually began to rhyme. Today it is instant. A machine can generate a complete, competent, utterly anonymous website in the time it takes to pour a coffee. The herd no longer drifts together over years. It is assembled together, overnight, at scale.

I want to be careful here, because I am not standing outside this. I use these tools every day. I also hand-code a great deal of what I make, and I let the machine move me faster only where I am comfortable letting it, and nowhere else. That distinction is the entire craft. The machine serves my judgment; my judgment does not serve the machine. The moment those two reverse, you get speed, and you get the herd.

Because faster is not always better. This is the quiet heresy of the moment. We have confused the speed of production with the quality of the result, as though a thing made in a minute and a thing made in a week were the same object at different prices. They are not. The minute-made site is fluent and empty. No photograph that is truly yours, no decision that could only have been made by you, no soul a person on the other side of the screen could feel. It is design-shaped, the way a stock photo is friendship-shaped.

Here is the cost, stated plainly. When a machine builds your website from the same average it built your competitor's, you do not merely look generic. You disappear. You are folded into a herd of businesses that are all, technically, fine, and a customer's eye slides across every one of you and remembers none. Invisibility is the most expensive thing a business can buy, and right now it is being sold at a discount, dressed up as efficiency.

The way out has not changed, even as everything else has. It was always judgment, and judgment is now the only thing left that cannot be copied. One real photograph, taken in your actual shop, of your actual hands. One sentence only your business could honestly say. One structural decision, not a colour but a decision, that reflects how you genuinely think. A machine can execute all of it beautifully, once a human has decided it. What the machine cannot do is care what it is for.

I believe we are about to learn, collectively and the hard way, that taste is not a luxury layered on top of the work. It is the work. When production becomes free, the only thing of value left is the judgment of what to produce, and that judgment is stubbornly, expensively human. The studios that understand this will look like nothing else on earth. The ones that do not will look like everything else, which is the same as looking like nothing at all.

So the question I leave with you carries more weight this year than it did last. If a machine can build, in sixty seconds, a website indistinguishable from yours, then what, precisely, was yours? Answer that honestly, and you have found the only thing worth building around. Everything else is just the blue button, waiting for the next person to press generate.

Jonathan Ellis · Edmonton

Elevated, weighty. The AI-convergence thesis. Pairs with one composed, hand-made UI mockup, proof of the point.

A machine can now build, in about sixty seconds, a website indistinguishable from yours. So it is worth asking, with some seriousness: what exactly was yours?

For twenty years I watched sameness drift slowly, everyone borrowing from the same few sources until they began to rhyme. That drift is now instant. The herd is no longer forming over time. It is assembled overnight, at scale, from the average of everything the tools were ever fed.

I am not outside this. I use these tools daily, and I hand-code a great deal of what I make. I let the machine move me faster only where I am comfortable, and nowhere else. The machine serves my judgment; my judgment does not serve the machine. The moment those reverse, you get speed, and you get the herd.

Because faster is not always better. We have confused the speed of production with the quality of the result. The minute-made site is fluent and empty, no image that is truly yours, no decision only you could have made, nothing a person on the other side could feel.

When production becomes free, judgment becomes the whole of the work. Taste is not a luxury laid on top of design. It is the design, and now the one thing left that cannot be copied.

#design #AI #branding #Edmonton

Warmer, neighbourly, but keep the weight. A blue-button confession.

Good Day. Here is something I have been sitting with after twenty years in this work.

There is a blue button I keep meeting. The same centred headline above it, the same three cards below it, on a layout I have now seen ten thousand times. It is not that designers stopped trying. It is that the tools started deciding, and the tools have only one taste, the average of everything they were fed.

A machine can now build a complete, competent, completely anonymous website in the time it takes to pour a coffee. Which means a business can look perfectly fine and still vanish, folded into a herd of sites that are all, technically, fine, and all forgettable.

I use these tools too. But I let them speed me up only where I choose, and I still hand-build the parts that matter. Faster is not always better. The thing that keeps you findable is the thing a machine cannot fake, one real photo of your actual shop, one sentence only you could honestly say.

If a machine could build your website in a minute, what part of it was actually yours? That is the only part worth keeping.

Visual-first. The blue button is the motif. Carousel carries the argument.

Good Day. There is a blue button I keep meeting, same headline, same three cards, same layout, ten thousand times over.

The tools started deciding, and the tools have one taste: the average of everything. A machine can build an anonymous website in the time it takes to pour a coffee.

Faster is not always better. When production is free, judgment is the whole of the work, and the one thing that cannot be copied. →

Carousel · 7 frames
1Why everything looks the same.
2The same blue button. The same three cards. The same layout, ten thousand times.
3The tools started deciding. And the tools have only one taste: the average of everything.
4A machine can build a complete, anonymous website in the time it takes to pour a coffee.
5Fine-looking. And forgettable. Folded into the herd.
6Faster is not always better. The minute-made site is fluent, and empty.
7When production is free, judgment is the work. It is the one thing that cannot be copied.
#design #AI #webdesign #branding #Edmonton #yeg

Gravitas, unhurried. The blue button is the visual motif. Optional screen-record of look-alike AI sites; otherwise just you.

Length · 24s    Hook · A machine can build a website identical to yours in sixty seconds. So what was actually yours?
TimeVoiceoverOn-screenShot
0-4sA machine can now build a website identical to yours in about sixty seconds. So let me ask you something.what was actually yours?You, straight to camera, calm, near-black room, one warm light.
4-11sSame blue button. Same three cards. Same layout, because the tools have one taste: the average of everything they were fed. The herd is not forming slowly anymore. It is assembled overnight.·Slow montage of near-identical landing pages, or hold on you.
11-18sI use these tools too. But I let them move me faster only where I choose, and I hand-build the rest. The machine serves my judgment. Never the other way around.faster is not always betterCut to hands on a keyboard, or a hand sketch beside a screen.
18-24sBecause when anyone can produce anything in a minute, the only thing left worth having is the judgment of what to make. Taste is not on top of the work. It is the work.taste is the workBack to you. Hold the final line in silence.
Audio · Low, serious pad. No drop. Let the silence at the end carry weight.
Caption · When production is free, judgment is everything. Good Day from Edmonton.
Assets needed
  • · One composed, hand-made UI mockup (dark, one green action) for LinkedIn, proof of the thesis
  • · 7 carousel frames in brand tokens; the blue button as motif
  • · 24s single-take video (desk; optional look-alike-site screen record)
Flagship 02 · Humans in the Age of AI · From the Land & the Workshop · 3 min · posts 2026-06-27

The Greenhouse and the Machine

A greenhouse does not replace the gardener. It protects the harvest, and that is exactly how I use AI.

Good Day. It is late June in Alberta, which this year has meant rain that will not stop, the grey, drowning kind of month that turns a garden to mud. And yet tonight, like every night this week, I will pick strawberries. A full harvest, daily. Lettuce every evening, more than my family can eat. None of it should be possible in this weather. All of it comes down to one structure: the greenhouse.

A greenhouse does not grow the food for me. It does something quieter and more profound. It insulates. It protects. It keeps the downpour off crops that would otherwise drown, holds warmth through a frost that would otherwise end the season, and gathers what little sun this month offers into enough. It does not remove the gardener's work, if anything it adds to it. More growing weeks. More to tend. More to pick. A greenhouse is not less work. It is more harvest, and more work, and, in the end, more good.

I have come to realise this is exactly how I use artificial intelligence. Not as a replacement for the work, but as a structure built around it. Something that holds off the conditions that would otherwise drown the good crops, the drudgery, the cold administrative nights, the repetitive tasks that kill momentum the way a late frost kills seedlings. The machine is my greenhouse. It extends my season and shelters my best work, so that more of it survives to harvest.

Notice what the greenhouse does not do. It does not decide what to plant. It does not taste the strawberry, or choose to give the first ripe one to my daughter, or know why this particular row matters more than that one. It changes the conditions, never the care. And the gardener who fears the greenhouse has misunderstood it entirely. It was never a threat to the craft of growing. It is the thing that lets the craft survive a hard June.

So when someone tells me they are afraid this technology will replace the human in their work, I think of the rain outside and the fruit inside. The fear assumes the structure does the growing. It does not. It protects the conditions so the human can do more growing, in worse weather, for more of the year. The danger was never that the greenhouse would replace the gardener. The danger is the gardener who refuses to build one, and loses the whole season to the storm.

There is real discipline in this, the same as on the land. A greenhouse left unattended will cook its own crop; too much of a good thing is its own kind of frost. You learn to vent it, to watch it, to know which days it helps and which days you open the doors and let the real weather back in. I use these tools the same way, deliberately, where they shelter the work, and never so completely that I stop feeling the soil. Faster is not the goal. More good, brought safely to harvest, is the goal.

I think the future of this work belongs to the people who treat these tools the way a good grower treats a greenhouse. As protection, not replacement. As a way to extend what is alive, rather than automate it away. The machine holds the weather. The human still chooses what to grow, and tends it, and gives the best of it away. That was always the point of a harvest. It still is.

It is raining hard as I write this, and I am not worried about tomorrow's strawberries. That is what a greenhouse buys you, not less work, but a harvest the storm cannot take. I intend to use every tool I am given in exactly that spirit, and not one inch further.

Jonathan Ellis · Edmonton

The vulnerable, visionary register. Reframes the AI fear through protection and harvest, not replacement. No hype.

It is late June in Alberta, and it will not stop raining. And yet tonight, like every night this week, I will pick a full harvest of strawberries. Lettuce, more than we can eat. In this weather, none of it should be possible. All of it comes down to one structure: the greenhouse.

A greenhouse does not grow the food. It insulates. It protects. It keeps the downpour off crops that would drown, holds off the frost, gathers what little sun there is into enough. It does not remove the gardener's work, it adds to it. More weeks, more to tend, more to pick. Not less work. More harvest, more work, and more good.

This is exactly how I use AI. Not as a replacement for the work, but as a structure around it, something that holds off the conditions that drown the good crops: the drudgery, the cold administrative nights, the repetition that kills momentum the way frost kills seedlings.

Notice what the greenhouse does not do. It does not decide what to plant, or taste the fruit, or know why this row matters. It changes the conditions, never the care. The gardener who fears it has misunderstood it.

The machine holds the weather. The human still chooses what to grow, tends it, and gives the best of it away. That was always the point of a harvest. It still is.

#AI #automation #design #Edmonton

Most personal register. The land and the weather do the emotional work. Neighbourly, a touch confessional.

Good Day. It is late June in Alberta and it has not stopped raining, the kind of month that turns a garden to mud. And yet tonight I will pick strawberries again. A full harvest, every day this week. Lettuce more than we can eat. The only reason is the greenhouse.

A greenhouse does not grow the food for me. It protects it. It keeps the downpour off the crops that would drown, holds the warmth through a cold night, and makes the most of what little sun we get. It is not less work, it is more. More weeks, more to tend, more to pick. More harvest, and more good.

I have realised that is exactly how I use AI in my work. Not to replace what I do, but as shelter around it, keeping off the dull, repetitive weather that drowns the good work, so more of it survives. The machine changes the conditions. It never decides what matters, or tastes the fruit, or gives the first ripe strawberry to my daughter.

People are afraid these tools will replace the human. But the greenhouse was never a threat to the gardener. It is what lets the gardener bring in a harvest the storm would otherwise take.

Strongest b-roll lane. Rain on the glass, the harvest basket, hands in soil. Caption is lyrical; carousel carries it.

Good Day. It is late June in Alberta and it will not stop raining. And yet tonight I will pick a full harvest of strawberries, because of one structure: the greenhouse.

A greenhouse does not grow the food. It protects it. Keeps off the downpour, holds back the frost, makes the most of little sun. Not less work, more harvest, more work, more good.

That is exactly how I use AI. As shelter around the work, never a replacement for it. The machine holds the weather. I still choose what to grow.

Carousel · 7 frames
1The greenhouse and the machine.
2Late June in Alberta. Rain that will not stop. And a full harvest, every single night.
3A greenhouse does not grow the food. It protects it.
4Keeps off the downpour. Holds back the frost. Makes enough of little sun.
5Not less work, more harvest, more work, and more good.
6That is exactly how I use AI. Shelter around the work, never a replacement for it.
7The machine holds the weather. I still choose what to grow, and who to give it to.
#AI #homestead #greenhouse #design #Edmonton #Alberta

His signature format, at its best. Single take in the greenhouse with the rain audible, or VO over harvest b-roll. The rain outside and the fruit inside is the whole story.

Length · 30s    Hook · It will not stop raining in Alberta. And yet I am picking strawberries every night this week.
TimeVoiceoverOn-screenShot
0-5sIt is late June in Alberta and it has not stopped raining. The kind of month that turns a garden to mud. And yet, tonight, like every night this week, I am picking strawberries.the greenhouse & the machineRain on the greenhouse glass from inside, then a basket of fruit. Warm light.
5-13sThe only reason is this structure. A greenhouse does not grow the food for me. It protects it. Keeps the downpour off the crops that would drown. Holds back the frost. Makes enough out of a little sun.·Slow pan along the rows. Zoom into a ripe strawberry beaded with condensation.
13-23sAnd this is exactly how I use AI. Not to replace the work, as shelter around it. Keeping off the dull, repetitive weather that drowns the good work, so more of it survives to harvest.protection, not replacementHands picking, placing fruit in the basket. Unhurried.
23-30sThe machine holds the weather. I still choose what to grow, and tend it, and give the best of it away. That was always the point of a harvest. It still is.I still choose what to growHand the first strawberry to your daughter, or hold it to the light. End in the rain-sound and quiet.
Audio · Real sound, rain on glass, a basket, birds, under a soft warm pad. Let the weather carry it.
Caption · I use AI like I use a greenhouse, protection, not replacement. Good Day from the rain in Alberta.
Assets needed
  • · Greenhouse b-roll in the rain: glass, rows, a ripe strawberry, the harvest basket, handing fruit to your daughter
  • · 7 carousel frames in brand tokens
  • · 30s single-take or lightly-edited greenhouse video with natural rain sound
Flagship 03 · The Business of Trust · Field Notes · 3 min · posts 2026-06-28

Twenty-Four Thousand Pages

I have touched perhaps twenty-four thousand pages in twenty years. Almost everything they were for has quietly disappeared.

Good Day. I have tried, more than once, to count the web pages I have touched in twenty years of this work. Designed, rebuilt, migrated, repaired. The honest answer is that I cannot, but the number lives somewhere near twenty-four thousand eight hundred, and whatever the true figure is, it is large enough to have shown me something most people never get to see: how completely the purpose of a website has changed beneath us, while the thing kept the very same name.

When I started, a website was a library. You built page after page after page, because the website's job was to hold everything a business knew and to prove, by sheer thoroughness, that the business was real. The site was the credential. It was where a stranger went to decide whether to trust you, and trust was measured in completeness, the more you documented, the more substantial you appeared. We built vast, patient archives, and that was the work, and it was good work.

Almost none of that is true anymore, and the shift happened so gradually that few people noticed the ground move. A website is no longer a library. It is a conduit. Its job is not to hold everything you know; it is to carry one person, with as little friction as possible, from interest to action, a purchase made in a moment, a contact request captured before the impulse fades. The archive became a hallway. The credential became a checkout.

I find this genuinely remarkable, because the trust did not disappear. It moved. People no longer build their confidence in you by reading twenty pages of history. They form it in seconds, from the feel of the thing: how fast it loads, how clear the next step is, whether it respects their time. Trust used to be something you proved with volume. Now it is something you signal with restraint. The site that helps you is no longer the one that says the most. It is the one that asks the least of the person trying to buy.

Most businesses are still building the old website. They are filling a library, because that is what a website was the last time they thought hard about it, adding pages, history, paragraphs of reassurance, all of it pointing inward, all of it serving the owner's sense of substance rather than the customer's need to act. They are constructing a magnificent archive directly in front of a customer who only ever wanted the door.

Touching that many pages taught me to see the few that actually carried weight. In any project, large or small, almost everything is archive and a very little is conduit, and the entire art is telling them apart, then having the nerve to clear the archive away so the conduit can breathe. A city's website and a corner bakery's are governed by the identical truth: know the one thing this person came to do, and remove everything standing between them and doing it.

There is a kind of grief in this for someone like me, who loved the library, who took real pride in the deep, complete, beautifully organised archive. But the work is not nostalgia. The work is to serve the person on the other side of the screen as they actually are now: in a hurry, on a phone, deciding in seconds. They did not come for the library. They came to do one thing. Everything else, however lovingly made, is in their way.

So I no longer ask a client how much we should put on their website. I ask what one thing a visitor most needs to do, and how much we can remove so they can do it. Twenty years and twenty-four thousand pages, and the lesson at the end of all of them is the smallest one. Build the door, not the archive. Almost everything a website used to be, it no longer needs to be, and that is not a loss. It is permission to finally get out of the customer's way.

Jonathan Ellis · Edmonton

Authority through scale, honestly framed (pages touched over a career). Lands on the conduit doctrine. Calm, unshowy.

I have tried to count the web pages I have touched in twenty years, designed, rebuilt, migrated, repaired. I cannot, honestly. But it lives somewhere near 24,800, and that is enough to have shown me something most people never see: how completely the purpose of a website has changed beneath us, while it kept the same name.

When I started, a website was a library. You built page after page, because the job was to hold everything a business knew and prove, by thoroughness, that it was real. The site was the credential. Trust was measured in completeness.

Almost none of that is true now. A website is no longer a library. It is a conduit, built to carry one person, with as little friction as possible, from interest to action. The archive became a hallway. The credential became a checkout.

The trust did not disappear. It moved. People form it in seconds now, from the feel of the thing, how fast it loads, how clear the next step is, whether it respects their time. Trust used to be proved with volume. Now it is signalled with restraint.

So I no longer ask a client how much to put on their site. I ask what one thing a visitor most needs to do, and how much we can remove so they can do it. Build the door, not the archive.

#webdesign #strategy #Edmonton #design

Story-led, reflective. A career-spanning number, then the warm landing on restraint.

Good Day. I have tried to count the web pages I have touched in twenty years of this work, built, rebuilt, migrated, repaired. I cannot, truthfully. But it is somewhere near twenty-four thousand. Enough to have shown me something strange: the whole purpose of a website has changed underneath us, and it kept the same name the entire time.

When I started, a website was a library. Page after page, because the job was to hold everything you knew and prove, by sheer thoroughness, that you were a real and serious business. The website was your credential.

That is mostly gone now. A website today is a conduit, built to carry one person, as smoothly as possible, from interest to action. A quick purchase. A contact request, captured before the moment passes. The archive became a hallway.

And here is the part I love: the trust did not disappear, it moved. People decide whether to trust you in seconds now, from how the thing feels, how fast it loads, how clear the next step is. Trust used to be proved with volume. Now it is shown with restraint.

So I no longer ask what we should add to a website. I ask what one thing a visitor came to do, and how much we can clear away so they can do it. Build the door, not the archive.

Number-led hook (mono numerals on screen). Carousel tells the then-and-now story.

Good Day. I have touched somewhere near 24,800 web pages in twenty years. Enough to watch the whole purpose of a website change beneath us.

It used to be a library, page after page, proving you were real. Now it is a conduit: carrying one person, smoothly, to one action.

The trust did not disappear. It moved. It used to be proved with volume. Now it is signalled with restraint.

Carousel · 7 frames
1~24,800 pages, in twenty years.
2Enough to watch the purpose of a website change, while it kept the same name.
3Then: a library. Page after page, proving a business was real. The credential.
4Now: a conduit. Carrying one person, with no friction, to one action.
5The archive became a hallway. The credential became a checkout.
6The trust did not disappear. It moved, from volume to restraint.
7Build the door, not the archive.
#webdesign #Edmonton #yeg #design #strategy #smallbusiness

Number-driven hook, mono numerals for 24,800. Desk-shot; optional cut to clearing all but one object from a surface, archive to door.

Length · 27s    Hook · I have touched almost twenty-five thousand web pages. Here is what it taught me.
TimeVoiceoverOn-screenShot
0-4sI have touched somewhere near twenty-four thousand eight hundred web pages in twenty years. And it taught me one strange thing.~24,800 pagesYou to camera, calm. Large mono numeral on screen.
4-12sThe whole purpose of a website changed underneath us, and it kept the same name. It used to be a library, page after page, proving a business was real. That was the credential.then: a libraryHold on you, or a slow pan over a cluttered desk.
12-20sNow it is a conduit. Built to carry one person, with no friction, to one action. A purchase. A request. The archive became a hallway. The credential became a checkout.now: a conduitClear everything off the desk but one object. The gesture is the point.
20-27sThe trust did not disappear. It moved, from volume, to restraint. So now I build the door. Not the archive.build the door, not the archiveBack to you. Let the last line settle in silence.
Audio · Quiet, precise. A single low note. No build. The restraint is the brand.
Caption · Build the door, not the archive. Good Day from Edmonton.
Assets needed
  • · Large mono numeral title card (~24,800) in brand tokens
  • · 7 carousel frames in brand tokens
  • · 27s single-take video (desk + the clearing gesture)
02

The Archive · 2005 to Today

The Archive is your blog's history, dated posts running from 2005 to today, each written as if from inside its own moment, with no knowledge of what came after. A 2007 post does not know what 2026 knows. That is what makes it real.

An honest note on backdating: dating a post to the day the events happened is legitimate, it is memoir, not deception. Google will still see when each page is first published, so this does not fake the age of the domain. What it does build is genuine depth, a credible body of work, and twenty years of internal links and topical authority. We publish the truth, dated to when it was true.
Written in full · 22 of 110
2005-07-24My First Real Deadline Came at 250 km/hI graduated in the spring. By July I was printing a racetrack.
Inaugural Champ Car weekend at the Edmonton City Centre Airport, July 2005. Print still rules; the web is only beginning to be taken seriously.

Good Day. I graduated from DevStudios this past February, top of my class, with honours, and I thought that meant I was ready. Then I spent the spring and summer printing a racetrack, eighteen hours a day, and I learned what ready actually means.

A man named Corey Gauveau interviewed me and hired me on the spot. He promised I would be well fed, well managed, and handed the experience of a lifetime, and every part of that turned out to be true. On my first day he passed me a red binder, a hundred pages thick, and said, in effect, these are the client orders, everyone who paid for track graphics and sponsor signage and paddock and booth space, so call them, find out what they need, design it, print it, and go. That was the entire brief. Trial by fire, in the best way a young designer could ask for.

The job was the inaugural West Edmonton Mall Grand Prix at the City Centre Airport, the first time open-wheel racing has come to Edmonton, a temporary circuit laid across the runways in our own backyard. I handled the graphics. All of them. Track graphics, wayfinding, the grandstand banners, the client signage, the markings on the tarmac, the thousand things a crowd of two hundred thousand never once thinks about, precisely because they are done well. Windship Aviation, the company that took me on, builds hot air balloons the rest of the year, and I was meant to be initiated with a balloon of my own, except I was too buried in print to stop for it.

We had a printer ten feet wide, and I have never been so intimate with a machine. The largest pieces ran sixty feet long and forty feet tall, several of them, the grandstand banners, and at that scale a misaligned file is not a small mistake on a screen. It is an enormous banner that is wrong, in front of everyone, with no undo. I learned to respect the timeline I had drawn, and to hold it even as clients kept adding to that binder.

It rained on opening day, hard, the way Alberta rains in July. I stood at the edge of the paddock with water running off the brim of my hat and watched everything we had made get tested by weather and crowd at the same moment. Some of it I would do differently. Most of it held.

And then the cars. We had access to the pits, and a vantage over the back corner that fed into them, and I want to try to tell you what it is to stand a few feet from a Champ Car at full song. These machines lose their grip if they go too slow, so a driver comes into the pit at a brutal speed and brakes at the last possible instant, landing each tire on a square barely an inch across. Precision at that velocity, chosen on purpose, three feet from where I stood. Everything I had been taught about composition and hierarchy suddenly had a heartbeat.

Three months of eighteen hour days will strip the school right out of you and leave only the craft. I came out the far side knowing things no classroom teaches: that a deadline is a form of respect, that scale changes absolutely everything, and that the work the crowd never notices is the work holding the whole day up. I am twenty-two years old, and I have printed a racetrack. I do not believe I will ever be intimidated by a brochure again.

Something is shifting in this trade, too, and I can feel the edge of it. The web is becoming a real place to do the work, not merely an afterthought bolted to the print. Standing on that tarmac, watching machines built for one purpose move faster than anything I had ever seen, I had the distinct feeling that our own tools are about to start moving like that, and I mean to be ready when they do.

The grandstands are coming down now. The runway is a runway again. And I am keeping a photograph of that ten-foot printer, because whatever I become in this work, it started here, at the track, in the rain, three feet from something extraordinary.

Jonathan Ellis · Edmonton · July 2005
2007-07-09The Glass in My PocketApple shipped a telephone last month. I think it just rewrote my job.
Weeks after the first iPhone (June 2007). No App Store yet, no Android; Jobs is pitching web apps. The mobile web suddenly renders real sites.

Good Day. Apple shipped a telephone a few weeks ago, and I have not stopped thinking about it since. I am two years into this work, and I am quite certain I have just watched the ground move under all of us. It is the most exciting thing to happen to my trade since I entered it.

Here is what thrilled me. It renders real websites. Not the stripped, grey, text-only mobile pages we have all been grudgingly making, but the actual site, the one I designed for a monitor, sitting in the palm of a hand, and you pinch it with two fingers to bring it close. The web has come off the desk, and I do not think the trade has fully grasped yet what an opening that is.

Every site I have ever built quietly assumes a person seated at a desk, with a mouse and a wide screen and a little patience. Every one of those assumptions just became optional, and I find that liberating rather than daunting. The screen is now four inches across. The mouse is a thumb. The patience is gone, because this person is standing in a line or on a bus, deciding in seconds. That is not a problem to fear. That is a cleaner, more honest constraint to design into.

We do not have a name yet for how to design for this, and I love that we do not. The clever people are already talking about building small web apps that feel like they belong to the device, and I intend to be among the first to try. The old comfort, it looks fine on my monitor, quietly stopped being good enough this summer, and that is precisely the kind of moment a designer should run toward, not away from.

My instinct, and I trust it, is that this rewards restraint, which happens to be exactly where my whole craft is already heading. A small screen punishes clutter instantly. It has no room for the ten things we usually pile at the top of a page. It forces the one question I build everything around: what is the single thing this person came to do? The desk let us dodge that question for years. The phone makes it the entire job, and I could not be happier about it.

I would far rather be early and right than late and safe, so I am going to start designing as though the small screen is the real screen and the desk is the luxury. I suspect that before very long that will simply be the work, and I intend to have been building it since the first summer.

Two years ago I was printing a racetrack at the City Centre Airport, learning what it means to make something at full speed and get it right the first time. Today I am holding a sheet of glass with an entire website living inside it. The trade is accelerating, and I mean to be at the very front of it.

Jonathan Ellis · Edmonton · July 2007
2005-02-25The Day I Walked Out of DevStudiosTop of a class of six, a five-month diploma, and a concrete crew behind me. Here is where it begins.
February 2005. Print still leads; Flash and the early web are where the energy is. A concrete finisher becomes a designer.

Good Day. I walked out of DevStudios this February, and I want to set the feeling down before it fades. I finished at the top of my class, and I am the one student of the six offered an internship, which is how a young man from a concrete crew finds himself about to design a Grand Prix.

Two years ago I was a concrete finisher, earning eighteen dollars an hour with my journeyman laborer's hands. I was good at it, and I told myself I would never get my certificate, because I did not want to become a lifer. What pulled at me was the high end, aesthetic side of the work, the design of it, except that on a crew a young man's job is to do, not to think. So in the fall of 2004 I left, and I put my own money, real money earned in the cold, into becoming someone whose entire job is to think.

I interviewed at every school I could find. DevStudios was the most expensive on my list and, strangely, the shortest, a two-year diploma compressed into five relentless months through their REV12 program. The moment I shook Grant Curry's hand I knew it was the place. That kind of acceleration is exactly how I am built. I left high school with a hundred and forty-five credits when a hundred will graduate you. I do not know how to attend something at half effort.

So I more or less lived there. DevStudios was one of the only schools with twenty-four hour access to the faculty, and I used every hour of it. There is a cot in that building that came to know me well. I would be at my desk by five in the morning, three hours of work already behind me by the time the others arrived at eight. I earned a great many perfect marks, and a few impossible ones above a hundred percent, not because I am gifted, but because I simply would not leave.

The thing that changed me was code. Kingston Fung taught us Flash and ActionScript, and the first time I made something move because I had told it to, in language, something opened in me that has not closed since. I came in believing design was print and polish. I am leaving knowing it is also logic and motion and systems, and that the web is about to become a real place to do the work.

I will be honest about one thing I carry. I hold a diploma, not a degree, no master's, no long letters after my name, and I know there are rooms where that will be counted against me. I have simply decided not to accept that arithmetic. Experience and relentless due diligence can stand in for years of training, and I intend to prove it on the work itself rather than on a transcript. I would rather be measured by what I can build than by how long I sat to learn it.

I believe design is the language through which I will change the things around me. Good design quietly solves a great many bad problems, and I want to spend my life solving them. That is not a small ambition for a former concrete finisher with a five-month diploma, and I am aware of that, and I am walking toward it on purpose.

The internship is at Windship Aviation, and the work, of all things, is a Grand Prix. I have no idea yet what it will ask of me. I only know that I walked out of that school certain of one thing. I am exactly where I am meant to be, and I am only just beginning.

Jonathan Ellis · Edmonton · February 2005
2005-09-19The Things a Crowd Never SeesThe wayfinding, the angles cut for a camera, the typo caught at three in the morning. The work that disappears into a good day.
September 2005, weeks after the inaugural Grand Prix. Reflection on the invisible craft of signage and broadcast graphics.

Good Day. The Grand Prix is weeks behind me now, and the thing I keep returning to is not the banners everyone saw. It is the work nobody will ever notice, which I am coming to believe is the truest measure of the craft.

Because it was Edmonton's first year, a lead designer who had worked the Australian Grand Prix came and stood beside me, one on one, through part of it. That kind of company is its own education. You learn more in a week at the elbow of someone who has done it than in months of doing it blind, and I will not soon forget the generosity of it.

Most of my pride from those weeks is unglamorous. A couple of us in a back room, weeding vinyl by hand, a plotter cutting wayfinding onto sheets of Coroplast, stack after stack of signs, and the quiet, enormous task of knowing exactly where each one belonged. We got every last one done, in time. At that scale, simply finishing is the accomplishment nobody applauds.

Exhaustion is its own hazard in this work. On a twenty hour shift, staring at the same screen, words begin to blur into one another. We caught a washroom sign at the last second that, with a single missing letter, read as something far less dignified. We laughed, and we fixed it, and I learned that proofreading is not a step you perform once. It is a discipline you hold even when your eyes have stopped cooperating.

Then there are the things designed for a camera rather than a person. The graphics on the ground are not printed square. We set them on a deliberate angle, judged against where the cameras would sit, so they read true on a broadcast. The logos around a hairpin are stretched, sometimes as much as four hundred percent wider than the mark itself, because a camera sweeping past at speed compresses them back into shape. I was astonished at how far you must distort a thing for it to look correct.

That is the real secret of it. We were not designing for the eye in the stands. We were designing for perception itself, for the angle and the speed and the lens, giving each logo its best possible chance in the half second it would live on a screen. None of it survives if you do it in a hurry. You take your time, or you get it wrong, and there is no rushing perception into place.

It is invisible, and it matters, and those two things are not in tension. The wayfinding that gets a stranger from a parking lot to their seat, the angle that makes a logo land, the missing letter you caught at three in the morning, none of it is glamorous and all of it is the job. I suspect this instinct, to sweat the part nobody will ever credit you for, is the one I will carry the furthest.

A great many people had a wonderful day at that track and never once thought about how they found their seat. That is precisely the point. The best of this work disappears into a good day, and I am proud to have made some of it vanish.

Jonathan Ellis · Edmonton · September 2005
2005-10-28Ink, Lights, and Two in the MorningA ten-foot printer, three hundred feet of vinyl lost to a colour drift, and the night I learned design is a symphony.
October 2005. The physical craft of large-format print, colour calibration, and respect for big machines.

Good Day. I find myself, this autumn, missing a machine. Specifically a printer ten feet wide, the one that turned my files into a racetrack, and I want to write down what it taught me before the memory cools.

It was a great bubble jet, fed by ink tanks that held two liters each, which you mixed by hand. A heat platen ran beneath the canvas to dry the ink as it laid down. The rolls were ten feet wide and weighed three hundred pounds, loaded by hand. The print head alone was something near sixty-five pounds, and once it was moving, its inertia was enough to take a careless person off their feet. You do not approach a machine like that casually. You learn its weight and its temper.

It was hot from the platen, loud enough to fill a room, and the smell could turn your stomach on a long night. And yet I loved being near it, because it carried a particular air of authenticity. What I had drawn on a screen was becoming real, at scale, in front of me. There is a seriousness to that which a glowing monitor cannot give you.

The stakes were physical and unforgiving. A sixty foot banner is printed in four passes, each ten feet wide. If the third pass of four carries a flaw, you have not lost a tap of the undo key. You have lost a hundred and twenty feet of vinyl, sometimes more, along with everything already printed on it. You learn to watch a print the way a surgeon watches a wound.

We burned about three hundred feet of vinyl once, and I want to be precise, because it matters. That was the machine, not the hand. On a late night print the colors drifted, and the work lights played tricks on our eyes, and only later did we see how far the color had wandered. So I learned color calibration the hard way, from screen to print head and back, how to remix, how to reset, how to make what you see become what you actually get. It is one of the most useful things I know.

Those late nights with the machine have a quality I have not found anywhere else. Past a certain hour you are running on something beyond energy, on passion and fumes and the simple refusal to leave a job unfinished. The machine does not care that you are tired. It asks only that you get it right.

I will carry this for the rest of my career. Whenever I ask for print in the years ahead, I will know the back end of it. I will know what a great press demands, what a wide format banner printer can and cannot do, how ink density and calibration and a clean set of nozzles decide whether a thing sings or smears. You design differently once you have stood beside the machine that has to make the thing real.

More than any single skill, it taught me that a finished piece is a kind of symphony. The file, the ink, the heat, the timing, the calibration, the steady hands at two in the morning, all of it has to arrive together, or none of it arrives at all. I did not expect a printer to teach me how design actually works. It turned out to be one of my finest instructors.

Jonathan Ellis · Edmonton · October 2005
2005-12-15What School Could Not Teach MeThe lowball offers, the impostor years, and the lessons that only the field can teach.
December 2005, closing the first year out of school. Pricing, worth, and standing in a room.

Good Day. My first year out of DevStudios is closing, and I want to name the things the school could not teach me, not as a complaint, but because they turned out to be the lessons that mattered most.

School gave me mock interview after mock interview, and they were genuinely good. They built the conversation and the confidence. What they could not prepare me for was the number on the other side of the table. I came from concrete, where I earned eighteen dollars an hour with my hands, and I had invested twenty thousand dollars of my own money, and ten thousand more in hardware, to become a designer. I would win an interview cleanly and be offered twelve or thirteen dollars an hour as though it were a generous gift.

I turned down a great many of those offers on principle, until honesty requires me to admit that desperation eventually won a round. I took a job at thirteen sixty-five an hour, briefly, at the Running Room, and I never once stopped hunting while I held it. Three months later I found work at eighteen dollars, exactly where I had judged my worth to be, and from there it has begun to climb. The lesson was not patience. It was refusing to accept someone else's low estimate of the work as the truth.

There is a quieter thing school could not teach me, which is how to stand near greatness without shrinking. I would study the people I admire, Edward Tufte and the way he makes data honest, the restraint that Apple and Jonathan Ive put into the world, the agencies producing work I could scarcely believe, and I would feel like an impostor in my own trade. I have learned to keep my eyes forward for exactly this reason. When I look back at my own work, I find fault. When I look ahead, I find the next thing to become.

It is humbling, too, to measure what you can make alone against what a team of twenty makes together, and to feel the gap. I am one person. I have decided the gap is not a verdict on me. It is simply the reason to get better, and to be honest about what one careful person can and cannot do.

Two things I have had to actively unlearn this year. The first is saying yes to everyone. Yes is how a young designer agrees to fifteen dollars an hour and then, through scope that quietly tripled, earns three. I am learning that a yes without a scope is not generosity. It is a slow way to come to resent your own work.

The second is my own perfectionism. Perfection is the enemy of progress, and I believe that now, even as a committed perfectionist. I hold a high standard and I will not ship work I am ashamed of. But I am learning which small imperfections will never sink a project, and to let those ones go, so the thing can actually exist in the world rather than live forever on my desk.

If I could add anything to a design school, it would have almost nothing to do with software. It would be how to pitch, how to truly listen, how to find out what a client actually needs underneath what they ask for. How to set a fair price and hold it. How to carry yourself as a luxury rather than a bargain, and to sound confident even on the day you are just beginning. I am learning all of it the slow way, in the field, and I suspect that is the only place it can really be learned.

A year ago I was certain school had prepared me. It had, for the work itself. The rest, the worth, the pricing, the standing in a room, I am building now, one hard conversation at a time. I would not trade those lessons for an easier year.

Jonathan Ellis · Edmonton · December 2005
2006-02-21Everything Got GlossyWeb 2.0 arrived in gradients and reflections, and I loved every shiny minute. What the gloss was really teaching us.
February 2006. The Web 2.0 look takes over; colour-screen phones begin rendering real sites.

Good Day. Everything got glossy this year, and I will admit it openly, I loved it. The whole web turned to gradients and reflections and soft, candy-coated buttons, and after years of flat, careful print restraint, it felt as though the medium had finally decided to enjoy itself.

There is something almost impressionist about this Web 2.0 look, something modernist, a style we have collectively decided to attach to ourselves in a way we never quite had before. I have poured it into brands like Evolve Landscapes with real pleasure, leaning hard into the shine and the depth, into the sense that a screen could feel tactile.

The timing is not an accident. Phones are beginning to change. We are seeing Samsung handsets with proper colour screens that can render primitive versions of a website, and that small fact is quietly setting the whole study of user interface in motion. Suddenly there is a reason to think about how a thing looks and behaves on a piece of glass in someone's hand.

Clients have never seen anything like it, so every one of them wants it. It is a trend, plainly, and a fad, and I am clear-eyed about that even as I enjoy it. We are making things too bold, too cluttered, too shiny, and at times too distracting from the one thing the page is actually for.

Which is, I suspect, the gift hidden inside the gloss. I think this era will teach the whole field to focus on what matters, on the single main actor in a design, and to treat everything else as supporting cast. Because the truth I keep relearning is that design is less about adding things and more about tastefully removing them, to create attention and reduce distraction.

So I will ride this shine while it lasts, and learn what it has to teach. Trends are not the enemy. They are how a medium tries on its new possibilities. The discipline is to enjoy them fully and still know, underneath it all, which of them you will choose to keep.

Jonathan Ellis · Edmonton · February 2006
2006-04-18The Year I Took the Web SeriouslyDreamweaver, CSS, and a back end that actually did something. The year the web stopped being decoration and became architecture.
April 2006. Tables giving way to CSS; the designer who also codes finds a rare middle.

Good Day. This is the year I started taking the web seriously, not as a lesser cousin of print, but as a craft with its own demands. I was coding in Dreamweaver, getting deep into HTML, watching CSS evolve into something you could actually build with, and realising the web deserved my full attention.

Along the way I noticed something that has shaped my whole approach since. Not many developers love design, and not many designers love to build. I had taken courses in development, intermediate programming, object oriented thinking, C and the rest, under an instructor named Mr. Koreshi at Centre High, and that grounding put me in a rare middle. I cared how a thing looked and I cared how it worked, and I refused to choose.

The first website I was genuinely proud of was for Mountain Industrial Safety, for a gentleman named Robin Posnikoff. In its day that was an enormous project, and finishing it well told me I belonged in this medium. Not long after came TNT Motorcycling, a riding school, and that one had a real back end, a booking and management system that held all their students. A site that did something, not just a site that sat there. That is when the web stopped being decoration to me and became architecture.

Print taught me a discipline I carry straight into the web. A friend of mine, Frank, used to remind me that some things are simply too small to read, and on the web you are fighting pixel densities and screen displays at every turn. In print we always tried to stretch the envelope of how small detail could go. On the web the lesson inverts. Never go too small, and find clever, quiet ways to fit the text without letting it overpower the page.

What resisted me most was the mastery of tables and CSS. It was a confusing realm of column spans and row spans, of structures that fell apart the moment a browser changed size, of writing exceptions for Internet Explorer and then exceptions to the exceptions. That fought me hard, and learning to win those fights is part of how I crossed over.

I did set the web down for stretches after this, drawn into branding and larger design work with developers at my side. But because I could speak their language, the design to development handoff became something I could shape rather than suffer. And I never truly left print behind. I simply kept it beside me, where it belongs.

Jonathan Ellis · Edmonton · April 2006
2006-06-27Flash and the Cult of MotionI built everything in Flash and loved it, even as I sensed the seams. The intoxication of motion, and the loophole at its heart.
June 2006. Flash and Director rule the animated web; the Player version chase never ends.

Good Day. Flash is everywhere right now, and I will confess I build almost everything in it. If I needed to find a place to rent, I would build a little Flash applet to do it. It did not matter what the task was, I was writing it in ActionScript, assembling it in Flash, and putting it up on my Hostgator server.

What I love is the object oriented nature of it, and the magic of tweening. You set a start state and an end state, and the software fills in every step between them on its own. To put that motion into a website, and watch it open an audience's eyes exactly where you wanted their attention, is intoxicating. Between Flash and, for a short while, Director, the animation side of this work has never been more alive.

Flash took the limits of tables and CSS and simply removed them, then added a flavour of motion on top. For a designer who came up fighting browser quirks, that freedom feels like the future arriving early.

And yet it worries me, even as I use it. Flash needs the Flash Player to run, and the Player is forever updating. If a visitor does not have the right version, you are back in the browser chase all over again, rewriting the same work several times to keep it alive. That is a nuisance dressed up as progress.

My clients, I think, believe Flash will become their backend world-runner, a fully customizable liquid canvas that auto-forms to whatever they need, animated and database-driven and endlessly clever. I understand the dream. I am not certain the foundation can carry it.

Because here is what Flash is quietly teaching me. Security matters. The way this technology sits inside the browser opens loopholes, and I suspect that, over time, those loopholes will be its undoing rather than its update cycle. I will enjoy every animated minute of it. I will also not be surprised when something more open and more honest takes its place.

Jonathan Ellis · Edmonton · June 2006
2006-09-12Designing for the Wild, Democratized WebSuddenly everyone had a page and everyone was a designer. Holding taste in a loud and crowded room.
September 2006. MySpace and the early social web; the word designer comes to mean anyone with Word.

Good Day. Suddenly everyone has a page. If a business does not have a website, it is hungry for one, often without quite knowing what one is for. MySpace is here, the early social experiments are stirring, and the whole idea of a web presence has gone from rare to expected almost overnight.

Designing in this democratized moment is a strange and interesting thing, because everyone now believes they are a design expert. The word designer has come to mean anyone with a copy of Word. I have lost count of the people who have asked me to build them something like MySpace, and at this point in my life I am not the developer I intend to become, so building a MySpace would be an enormous undertaking I am neither equipped for nor drawn to.

So I keep my focus on the design itself, which in a loud and crowded realm is genuinely difficult. I have found myself drifting back toward print during this phase, where taste still has room to breathe, while keeping a close watch on how things move in Flash, in CSS, in plain HTML, and in this JavaScript that keeps gaining ground.

There are trends I simply refuse to follow, and I hold that line on purpose. Starbursts begging for attention, stacked on top of glossy buttons, became a plague, and I would not touch them. Comic Sans became fashionable in its own way, and I would not set a word in it. You can be inventive without reaching for the cheapest trick in the room.

Did I find something beautiful in the chaos? Honestly, I am not sure I did, and I am not sure I was even looking at it that way at the time. I was heads down, holding a standard, trying to keep clean work clean while the whole web shouted around me.

What the era was really for, and who it served, I could not have told you then. But it taught me something durable about taste. When everyone is suddenly allowed to make things, the value of restraint does not fall. It rises, because it becomes rare.

Jonathan Ellis · Edmonton · September 2006
2006-11-30Print Is Not Dead, But It Is QuieterNot shrinking, exactly, just quieter as the web arrives beside it. What print taught me about permanence and proportion.
November 2006. The web becomes a parallel cost to print; the analog beauty of a thing you can hold.

Good Day. People keep saying print is dying, and I do not think that is quite the truth of it. Print budgets are not collapsing so much as the web is arriving as a new cost beside them. Companies are doing both for now. The hard choice, the one where someone looks at the numbers and cuts print because the web is winning, that comes later. We are not there yet.

What I miss already, as the attention shifts, is the permanence of a printed piece. Once a thing is printed it is, in a way, immortal. There is something timeless about holding a physical copy that no power outage and no broken screen can take from you. If the lights go out you can build a fire and read it by that. There is an analog beauty in that which the web has not yet learned to offer.

The print principle I carry into everything digital is proportion, the golden ratio, the quiet mathematics of how a thing sits in its space. That does not change when the medium does. Good proportion is good proportion on paper or on glass.

I cannot say I have had a single farewell piece, a last great print job that felt like goodbye. But laying out a magazine for a freelance client this year, I did feel something archaic in it, a sense that the readership had quietly moved on while we kept setting type. Perhaps that was a small goodbye after all.

The people most certain about print used to say that nobody would ever read their news on a screen. I notice that more and more of us now get our news exactly that way. I suspect, in time, the printed paper will become the rarer thing, not the default.

So I am not mourning print. I am keeping it close, and carrying its lessons forward, because the medium that taught me permanence and proportion still has a great deal to teach the medium that is about to inherit the world.

Jonathan Ellis · Edmonton · November 2006
2007-03-08The Fold Is a Lie We Tell ClientsThe fold became a superstition. The target-ring game I use instead, and why a website is a conduit, not a destination.
March 2007. The above-the-fold debate at its height; heat maps reveal how people really read.

Good Day. There is a phrase I keep hearing in client meetings, above the fold, and I want to talk about it plainly, because it has quietly become a kind of superstition. The fold is just an abstract way of saying, put the important message first and keep the actionable pieces visible. That is sound advice. The trouble is what people have built on top of it.

Somewhere along the way the fold became magic. People decided that anything above it was golden and anything below it was lost, and that belief gave us these enormously tall, scrolling pages stuffed with everything, on the theory that surely people will scroll. And in this era, sometimes they do. But the obsession bothers me, because a person interacts with far more than the first thing they see. The top of your page is a first impression. The real question is how you earn the trust to back that impression up.

So when a client insists that everything must live in the fold, I do not argue. I play a game with them instead. I draw three rings, like a target, and we put every idea in the outer ring. Then I say, you may move five ideas inward, so choose. Then from those five, or three in a smaller room, we move exactly one to the centre. We watch the targeting happen, the shift from throwing macaroni at a wall to throwing one true thing, and knowing whether it hits.

It is progression and strategy in service of clarity, because a wealth of information becomes a poverty of retention. That is the line I come back to again and again with clients. Say everything and they remember nothing.

I have also watched it happen. I used to run heat trackers on my sites, the kind that slowed everything to a crawl, and I would switch them on for a while just to see. You learn quickly how people actually move, what they truly click, how fast they scroll, and you see that when someone races past a paragraph without pausing, they read none of it. They caught a word or two, no more. Watching that, the fear of the fold simply falls away.

These days I do not talk about the fold at all. I talk about the priority of the structure, and the real need of the site. Because a website is a frictionless conduit, a way to carry a person from where they are to the thing they came to do. They might read your story and check your reviews, but only on the way to an objective. The page is the middle of the journey, never the destination, and once you see it that way, the fold stops mattering entirely.

Jonathan Ellis · Edmonton · March 2007
2007-09-25Nine Fonts and a WorkaroundA September spent designing with only nine fonts, and the day real type will finally reach the web.
September 2007. Custom type still lives as images; web fonts are a wish, not yet a reality.

Good Day. It is the ninth month, so I set myself a small discipline this September, to design with only nine fonts for the entire month. I wanted to feel the constraint, and it taught me more in four weeks than a year of unlimited choice ever could.

The first lesson is the simplest and the most useful. No more than two fonts in a single design. I put all nine into a few pieces just to play, and they have their pros and their cons, but the constraint keeps you in a wheelhouse. You stop fretting over the unique character of a typeface and start working the things that are not limited.

With your choices narrowed, you create variety another way, through spacing and repetition, through alignment and proximity, through figure and ground, through playing with the individual letters themselves until they hold their own interest. Above all you learn to play with white space, because when the type is fixed, the room around it becomes your instrument. A constraint, used well, breaks creative block rather than causing it.

Typography matters enormously to me. I have something near six thousand fonts now, and the library never stops growing. Foundries like Linotype have been an education on their own. I love asking what makes a face read as regal rather than loud, quiet rather than outspoken, elegant rather than plain, because every one of those characteristics speaks for a brand. Pairing a brand with its true voice in type has become one of the genuine joys of my life.

The tools, I will say, have always been a frustration. There is still no good way to view a font library. You end up in Adobe Illustrator, squinting at a preview an inch wide and a quarter inch tall, trying to judge the details of one typeface among thousands. So I have built my own way around it, curating my own lists and even printing specimen sheets, so I can hold the type rather than fight the software.

What I want most, and what the web does not yet truly allow, is to put real type online. Today, to use a custom face, we still have to bake the title into an image, and that image is invisible to search, unfriendly to readers, and slow to load on a weak connection, so the headline arrives ten seconds late, if at all. The day we can set real type on the web, brand character will finally cross over into it, and a great deal of careful, intricate craft, every kern and ligature, will finally get to be seen.

Jonathan Ellis · Edmonton · September 2007
2007-11-14A Client Asked for a BlogDesignHouse wanted to publish for themselves. What early WordPress taught me about keys, weeds, and the human need to be heard.
November 2007. Early WordPress; handing clients the keys, and watching the garden grow over.

Good Day. A client asked me for a blog this month, and it turned into a small education. It was for DesignHouse, a salon, and they wanted to keep their clients up to date and, more than that, to push the content themselves, in their own words, on their own time.

They feared it would be hopelessly complex, and my job was to prove it would not. I built it on early WordPress, and it broke more than once, mostly because they would strip out the inline style tags whenever they edited. So I found a way to make the CSS hold without them, styles tied to standard HTML elements, so the thing stayed on brand even when they did not think about it. Getting them comfortable still took time.

I learned that written guides help a little, but the thing that actually works is direct support, walking a person through it, patiently, more than once. That is the real cost of handing someone the keys, and it is worth it, but you should know it going in.

I also learned the hard truth of a content management system. The moment you give a client control, they take liberties, because they do not see the structure the way the builder does. You hand over a beautiful, finished portfolio piece, and three months later you return to find it overgrown. Inconsistent posts, stray fonts creeping in, off-brand colours, all because someone needed the page to say a thing and did not much care how it looked while they said it.

It is like building someone a beautiful front and back garden, returning six months later, and finding it an overgrown forest because nobody once mowed or pulled a weed. Your careful work is still under there somewhere, hidden. You develop a thick skin about it, and you learn to photograph your work the day it ships, for the case study, before the lawn grows over.

And yet, for all the frustration, the blog revealed something I find moving. People need to be heard. They want to voice their thoughts in a way that presents them as the expert they are. We are storytellers, all of us, and a business that tells its story lets people feel included in how it thinks. That, in the end, is what a blog opens up. It is also, if I am honest, why I am beginning to want to publish my own. I have experience worth sharing with the designers coming up behind me, a record worth keeping, and a legacy I would like to craft on purpose rather than leave to chance.

Jonathan Ellis · Edmonton · November 2007
2007-12-20Two Years InStill a designer, still an impostor in my own head, and standing at a crossroads. What I would tell myself heading into 2008.
December 2007. Two years into the trade; the swing between great months and lean ones.

Good Day. Two years into this trade, and I want to set down what has surprised me, because the surprises have been the real teachers.

What surprised me most is how hard it is to find freelance clients consistently. I have been in and out of work, a couple of years here, a few clients there. When it is good it is wonderful, and when it is hard it is genuinely hard, and the swing between the two is steeper than anyone warned me.

By the close of the year, the thing I am proudest of is simple. I am still a designer. I am still here, still standing in the trade, and after the lean stretches that is not nothing.

I am still insecure, too. The impostor feeling has not left me. I do not always trust that I have what it takes to stay on the cutting edge of web design as fast as it moves. I can feel myself at a crossroads, tempted to bifurcate, to lean hard into brand design and marketing strategy and let the web evolve on its own without me.

But the work ethic and the research ethic that brought me here are still very much alive, and I trust those more than I trust my doubts. They are the part of me that does not quit when the clients are scarce.

If I could speak to the version of me walking into 2008, I would keep it plain. Keep growing. Keep doing what you are doing. Keep reading the books, keep challenging yourself with design-a-thons, and keep pushing hard, because hard work pays off. I do not have proof of that yet. I have a conviction, and for now that will have to be enough.

Jonathan Ellis · Edmonton · December 2007
2008-02-19jQuery and the Joy of Less CodePre-built modules that felt like magic, and the quiet worry of knowing less about my own code. Learning that tools always change.
February 2008. jQuery and a flood of libraries; the Lego brick where the foundation used to be.

Good Day. My toolkit is lean and serious this year, and at the centre of it sits jQuery, running on a Hostgator server. It lets me do things on the fly that feel close to magic, reaching for pre-built modules instead of writing and designing every component by hand, moving at a pace that makes me feel briefly invincible.

And yet that same speed has started to unsettle me, because I notice I know a little less about my own code than I used to. The moment jQuery arrived, a dozen libraries followed it, and I find myself reading more documentation, learning more syntax, forever. It is like trying to learn thirty languages at once, living in thirty countries in a single month, waking each day in a different tongue and spending it just working out what everyone is saying.

That is a real challenge, and overcoming it daily is its own skill. It has pushed me toward a more agile, more mindful way of working, and toward an honest question I now ask of every tool. Not is this clever, but is this what the client actually needs.

I never stopped hand coding, and I do miss the challenge of building a thing from the ground up. It is the difference between digging the hole and pouring the foundation yourself, and having a single Lego brick arrive that simply is the foundation. The brick is there for you, and it saves you, but you lose the quiet satisfaction of the labour that used to come first.

The trade-off, though, is real and worth it. Letting the tools carry the repetitive parts lets me put my attention where it matters. And it is teaching me a lesson I suspect I will need for the rest of my career.

Tools are always changing. The skill is not mastering any one of them forever. It is learning to integrate with whatever arrives next, to hold loosely to the syntax and tightly to the judgment, and to keep asking, through every new library and every new fashion, what the work in front of me truly requires.

Jonathan Ellis · Edmonton · February 2008
2008-05-06Designing Through a DownturnThe crash reached my clients, and taught me a discount habit I am still trying to break. The price is the price.
May 2008. The financial crisis spreads; budgets evaporate and negotiation becomes a reflex.

Good Day. The financial crash this year began in the States, and we have watched it from here with a certain distance, but the distance is not as safe as it looks. I have a client in Las Vegas who lost a great deal, and watching that up close taught my clients, and me, that nothing is certain, and that we had better be pragmatic in how we work.

This has been a downturn in more than money. People have stopped spending on design, and stopped valuing it the way they did a year ago. I have struggled to keep clients, watched budgets simply evaporate, and learned, out of necessity, how to stretch a dollar further than I thought possible.

It also pressed a bad habit into me that I am still trying to break. In desperation I began to discount, to bend on price when a client pushed, and once you start that, it is hard to stop. I want to say this plainly, as much to myself as to anyone. The price is the price.

You would not haggle over a Mona Lisa. You do not walk into a grocery store and negotiate the price of a pound of ground beef, or argue the cost of a gallon of milk. You decide it is worth it, and you pay, and you carry it home. Yet this downturn has quietly taught a whole market that they may negotiate a designer down, and too often, in a hard month, I have let them.

I am naming it because naming it is the first step out. The work has a value that does not move with someone else's anxiety, and treating it as though it does is a slow way to teach the world that craft is cheap.

So this is the year I learned both halves of the lesson at once. How to be lean and resourceful when money is tight, and how dangerous it is to confuse being generous with being undervalued. I have not mastered the second half yet. But 2008 made very sure I will never again forget the question.

Jonathan Ellis · Edmonton · May 2008
2008-08-12There's an App for ThatThe App Store opened, and I felt it in my hands before most. Why the real question was never app or website.
August 2008. The App Store launches; early imported iPhones, security, and Apple guarding its users.

Good Day. The App Store opened this summer, and I have been turning it over ever since from my home studio. I happen to have every early iPhone, imported from the States back when getting one into Canada meant wrestling with SIM card access, so I have felt this shift in my hands before most people here have touched it.

It is a slightly anxious moment and an exciting one at once. In building for the web, security has always weighed on me, protecting data, guarding everything passing through the gateways, making sure a site cannot be turned to nefarious ends. So what strikes me about the App Store is that, for once, someone else is watching too. A large company is choosing to protect its audience rather than leave them to the wolves, and I find that genuinely cool. It has quietly deepened my evangelism for what Apple is doing.

I believe apps are the future. Everything will have one, and the businesses without one will be left in the dust. So I have thrown myself into the design of apps, because the building of them is still a mysterious black box of Apple code I cannot yet see into. If I am honest, I wish I were building some of my own ideas into apps right now. I suspect a few of them would do very well.

I also think the App Store is about to warp what clients expect. They see that anyone can charge ninety nine cents and sell a million copies and make a million dollars, and they conclude that this is cheap and easy and quick. They do not see the ten million in research and development behind the overnight success. So once again I find myself explaining that cheap, easy, and free are not the same as good.

Here is the doubt I will admit. I am betting heavily on native apps, and I am not sure I am right. A web app, in the end, may do the very same thing, and building everything several times over, once for one platform and then again for the next, starts to look like a great deal of redundancy for its own sake.

What I am coming to believe is simpler than app or website. The only thing that truly matters is whether the tool works, whether it genuinely helps and actually saves a person time. If it does not, it is not a tool at all, it is a distraction. So I am steering my clients away from the question of app versus site, and toward the only thing that counts, the touchpoint where a customer comes to trust the brand and do the thing they came to do.

Jonathan Ellis · Edmonton · August 2008
2008-10-21When Budgets Vanish, Restraint WinsCutting to the core, finding the fat was never needed, and the difference between cheap and lean.
October 2008. Clients slash scope; the minimum viable version, done properly, becomes the plan.

Good Day. The budgets are vanishing this autumn, and to my own surprise, it is teaching me one of the most valuable lessons of my career so far. When a client cuts their scope, the easy reflex is to cut your service in equal measure, to give less because you are paid less. I have learned to do the opposite.

Instead of cutting, I focus. I ask what is most important, and we build a minimum viable version of exactly that, a fraction of the original plan, done properly, with a phased path to the rest. When revenue returns, they come back, and we add on. That reframe changes everything, because it turns a retreat into a plan.

And something unexpected happens along the way. Often, in cutting to the core, we discover that a piece they were certain they needed was never actually core to the business at all. We cut the fat, and the thing gets clearer, and the client trusts me more for having helped them find it.

That trust, it turns out, is the real product. Restraint as necessity, forced on us by a hard year, is quietly becoming restraint as philosophy, chosen on purpose.

I want to be precise about one distinction, because it matters. There is a difference between cheap and lean. Cheap is about paying as little as possible and getting as little. Lean can still be quite expensive. Lean is about removing everything that does not serve the goal, and what remains is usually far more effective for the cutting.

So I am grateful, in a strange way, for a season that took the budgets away. It is teaching me that the most useful thing I can offer a client is not more. It is the judgment to find the one thing that matters and the discipline to build only that, beautifully, first.

Jonathan Ellis · Edmonton · October 2008
2008-12-16The Web Grew Up This YearThe easy money left and the serious question arrived. Launching Forfame, and learning to make things under my own name.
December 2008. Year-end budgets gone; productizing my own craft when the client work thins.

Good Day. The web grew up this year, and so, I think, did I. The downturn has been a hard teacher, and I have felt it most as the year closes, applying for work heavily and watching client after client decide that design is a luxury they will revisit later.

The timing makes it worse. We are into the holidays, the year-end numbers are landing, and whatever budgets existed have already been consumed by the season. Trying to find new work right now is like knocking on doors in a building where every light is already off. Everything is shutting down for the year at exactly the moment I need it open.

But a lean season has a way of pushing you somewhere new. Rather than only chase the vanishing client work, I have started to turn my craft on myself, to productize what I can make rather than wait to be hired to make it.

So I launched a clothing line this year, called Forfame, and I have simply been having fun with it. With the client work thin, building something that is mine, a small business of my own, has been a genuine joy and a quiet kind of insurance.

That instinct feels important, more important than the line itself. When the market will not pay you to make things, make things anyway, and find a way to put them into the world under your own name.

The web grew up this year because the easy money left and the serious question arrived. Not what can I sell quickly, but what can I build that lasts, that is mine, that does not depend entirely on someone else's good quarter. I do not have that figured out yet. But 2008 made very sure I would start asking.

Jonathan Ellis · Edmonton · December 2008
2009-02-10Twitter and the Art of 140 CharactersA small box that sharpens everything inside it. How brevity changed my writing and my design.
February 2009. Twitter goes mainstream; words become the only thing you have.

Good Day. Twitter has me thinking about constraint again, and I find the limit thrilling rather than confining. You are given a small handful of characters and told to say something true in them, and after years of designing for endless space, that boundary feels like a gift.

It rhymes with the discipline I set myself with nine fonts, the same lesson in a different key. When you can only say so much, brevity stops being a style and becomes the whole task. You learn clarity, focus, voice and tone, and how saying less changes not only your writing but your design.

And there is a stripped-down honesty to it that I love. With no visuals to lean on, the words are all you have, so you choose each one with real care. Language, used that deliberately, becomes powerful out of all proportion to its length.

It is making me more creative, not less, because a hard constraint demands more of you, and I have always believed we should do hard things. A blank page of infinite room is easy to fill and easy to waste. A tight box forces you to decide what you actually mean.

I keep noticing how often this is the real shape of craft. Not more room, more tools, more words, but a chosen limit that sharpens everything inside it. The fold taught it to me. The fonts taught it to me. Now a hundred and forty characters are teaching it again.

So I am grateful for the small box. It is one more reminder that restraint is not the enemy of expression. Most of the time, it is the thing that makes expression land.

Jonathan Ellis · Edmonton · February 2009
2009-04-14An Ad Agency Inside a HospitalI turned an audiovisual room into a creative department, and helped a health group become Covenant. The most meaningful work yet.
Spring 2009. Caritas becomes Covenant Health; building an internal agency across fourteen facilities.

Good Day. This spring I did something I did not expect. I walked into a hospital's audiovisual department and set about turning it into an ad agency. The result is a new Creative Services Department inside Covenant Health, and helping build it has been the most meaningful work of my career so far.

The larger task was a rebrand. Caritas Health Group is becoming Covenant Health, and I have had the privilege of working on that transformation alongside a friend who serves as a vice president of communications, an ally who understood that good design is not decoration in a place like this. It is part of how an institution earns trust.

What we built out of that old AV room, based at the Grey Nuns and Misericordia hospitals, is a genuine internal agency, a creative function that can serve the whole organization rather than scramble job by job. We are carrying graphics and brand across fourteen facilities throughout Alberta, which is a scale I had not worked at before, and it asks a different kind of discipline. At that size, consistency is not a nicety. It is the brand itself.

Designing for healthcare has changed me. You are not making something cleverer than the competition. You are making something that meets a person on what may be a frightening day, and treats them with calm and clarity and respect. That responsibility sits differently in the chest than a commercial brief does.

I am still taking on freelance clients on the side, because I do not think I will ever fully stop, and the mix keeps me sharp. But the institutional work is teaching me something the freelance years could not, how to build a thing that outlasts me, a department and a standard that will keep serving long after any single project is done.

That is the part I am proudest of. Not a poster, not a logo, but a function, a way of working, set into an organization that cares for people. I came in to design a brand. I am leaving, eventually, having helped build something that will go on making good work when I am no longer in the room.

Jonathan Ellis · Edmonton · April 2009
How to record

Press and hold, read a post's prompt, then answer its seven questions out loud. Ramble, wander, repeat yourself. I write the finished post from what you say. Full sheets are in archive/recording-sheets.md.

The full 110-post timeline · expand any post for its seven questions
2005
02-25
The Day I Walked Out of DevStudios✓ written7 questions
Graduating top of your class with honours, what you believed design was then, and what you were afraid of.
  1. What do you actually remember about graduation day at DevStudios, the room, the weather, who was there?
  2. What did you believe, at twenty-two, that design was for?
  3. What were you most afraid of as you walked out with that diploma?
  4. Was there a teacher or a single project at DevStudios that changed how you saw the work?
  5. What did being top of your class actually feel like, and did it matter as much as you expected?
  6. What did you imagine your career would look like, and how wrong were you?
  7. If you could say one thing to that twenty-two-year-old, what would it be?
07-24
My First Real Deadline Came at 250 km/h✓ written7 questions
Already written, refine with any details I missed (people, near-disasters, the printer).
  1. Who hired you at Windship Aviation, and what did they see in a brand-new grad?
  2. Who else was on that crew, and is there a person from those weeks you still think about?
  3. What was the worst near-disaster on the ten-foot printer, and how did you save it?
  4. What was the single largest piece you printed, and where did it end up on the circuit?
  5. What did the paddock smell and sound like the first time you stood in it?
  6. Eighteen-hour days for three months, what kept you going, and what did it cost you?
  7. When the grandstands came down, what did you take away that you still carry?
09-19
The Things a Crowd Never Sees✓ written7 questions
The invisible work, wayfinding, signage. A moment something nearly went wrong and how you caught it.
  1. What piece of wayfinding from the track are you proudest of, and why?
  2. Walk me through a sign or system that nearly failed, what happened?
  3. How did you catch it, and who helped?
  4. What did designing for a lost, hurried stranger teach you that school never did?
  5. What makes signage invisible when it works and obvious when it fails?
  6. Did anyone ever thank you for the invisible work, or is that the whole point?
  7. How does that wayfinding instinct show up in your web work today?
10-28
Ink, Lights, and Two in the Morning✓ written7 questions
The ten-foot printer; the physical craft of big print; what the machine taught you.
  1. Describe the ten-foot printer, what did it look, sound, and smell like?
  2. What were its moods, and how did you learn them?
  3. What is the hardest thing about producing at forty feet with no undo?
  4. What did a ruined print teach you that a perfect one never could?
  5. What did two in the morning alone with that machine feel like?
  6. Is there a craft from big print that the digital world has quietly forgotten?
  7. What did that machine teach you about respect for the work?
12-15
What School Could Not Teach Me✓ written7 questions
The gap between school and the job; the hardest lesson of year one.
  1. What did school prepare you for, and what did it completely miss?
  2. What was the hardest single lesson of your first year working?
  3. When did you first feel like a real designer rather than a graduate?
  4. What did a deadline teach you that a grade never could?
  5. Who or what humbled you that first year?
  6. What did you have to unlearn the fastest?
  7. What would you put in a design school that is not there now?
2006
02-21
Everything Got Glossy✓ written7 questions
Your take, as it happened, on the Web 2.0 look. Did you love it or distrust it?
  1. When did you first notice everything turning glossy and rounded?
  2. Did you love the Web 2.0 look, or did it bother you, and why?
  3. What was a project where you leaned into those gradients and reflections?
  4. What did clients ask for that they had clearly seen somewhere else?
  5. Looking back, what did that era get right about the web?
  6. What did it get wrong that we paid for later?
  7. What does the gloss of 2006 tell you about trends in general?
04-18
The Year I Took the Web Seriously✓ written7 questions
When you shifted from print-first to web-first; the learning curve and the resistance.
  1. What made you finally take the web seriously as a craft?
  2. What was the hardest part of moving from print thinking to web thinking?
  3. Do you remember the first website you were genuinely proud of?
  4. What did print teach you that made you a better web designer?
  5. What resisted you the most, tables, CSS, browsers, or clients?
  6. Who or what helped you cross over?
  7. What did you lose, if anything, in leaving print behind?
06-27
Flash and the Cult of Motion✓ written7 questions
Flash, what you built with it, what you loved, what already worried you.
  1. What did you build in Flash that you loved?
  2. What was intoxicating about motion on the web back then?
  3. What already worried you about Flash, even as you used it?
  4. Was there a Flash project that was pure joy to make?
  5. What did clients believe Flash would do for their business?
  6. When did you first sense it would not last?
  7. What did the Flash era teach you about substance versus spectacle?
09-12
Designing for the Wild, Democratized Web✓ written7 questions
The messy social web; a client who wanted a 'MySpace'; taste in a tasteless time.
  1. What was it like designing when suddenly everyone had a page?
  2. Did a client ever ask you to make them something like a MySpace?
  3. How did you hold onto taste when the whole web was loud and messy?
  4. What did the democratized web get right that the gatekeepers had missed?
  5. What was the worst trend you flatly refused to follow?
  6. Did you find anything genuinely beautiful in the chaos?
  7. What does that era say about who design is really for?
11-30
Print Is Not Dead, But It Is Quieter✓ written7 questions
Watching print decline; what you carried from print into the web.
  1. When did you feel print budgets really start to shrink?
  2. What did you miss most about print as it quieted?
  3. What print principle do you still use in everything digital?
  4. Was there a final big print piece that felt like a goodbye?
  5. What did the print-only people get wrong about the web?
  6. What did the web kids get wrong about print?
  7. What is permanent about good print that screens still cannot match?
2007
03-08
The Fold Is a Lie We Tell Clients✓ written7 questions
The fold fight with clients; your view then.
  1. What did clients believe about above the fold back then?
  2. Why did the fold bother you as an idea?
  3. What did you say to a client who demanded everything at the top?
  4. When did you first see real evidence that people scroll?
  5. What is the real fear hiding underneath the fold obsession?
  6. How do you talk about it with clients now?
  7. What other rules of that era turned out to be myths?
07-09
The Glass in My Pocket✓ written7 questions
Already written, refine with where you were the day you first held one.
  1. Where were you the first time you held an iPhone?
  2. What was the exact moment you realised the ground had moved?
  3. Who did you talk to about it, and did they understand?
  4. What did you do differently in your work within weeks?
  5. What did most of the trade miss in that first summer?
  6. What did you get wrong in your first predictions?
  7. What does that morning tell you about spotting a real shift early?
09-25
Nine Fonts and a Workaround✓ written7 questions
The frustration of designing type with nine fonts; the hacks you used.
  1. What did designing type with only nine fonts actually feel like?
  2. What hacks did you use to get real typography onto a screen?
  3. What was a project where the type fought you the whole way?
  4. Why does type matter so much to you?
  5. What did that constraint teach you that freedom later erased?
  6. When real web fonts finally arrived, what changed for you?
  7. What do designers with infinite fonts now take for granted?
11-14
A Client Asked for a Blog✓ written7 questions
Early CMS/blog projects; teaching clients to publish for themselves.
  1. Who was the first client to ask you for a blog, and why?
  2. What was it like teaching someone to publish for themselves?
  3. What did clients fear about being handed a CMS?
  4. What broke, and how did you fix it?
  5. Did giving clients the keys help the work or hurt it?
  6. What did early blogging reveal about people's need to be heard?
  7. How does that connect to why you publish now?
12-20
Two Years In✓ written7 questions
Two years into the trade, what surprised you most.
  1. Two years into the trade, what had surprised you most?
  2. What were you genuinely proud of by the end of 2007?
  3. What were you still insecure about?
  4. Who had become important to your growth?
  5. What did you believe about the future of the web then?
  6. What habit from those two years still serves you?
  7. What would you tell that version of yourself heading into 2008?
2008
02-19
jQuery and the Joy of Less Code✓ written7 questions
Your stack in 2008; the tools that made you faster.
  1. What was in your toolkit in early 2008?
  2. What did jQuery let you do that felt like magic?
  3. What did writing less code change about how you worked?
  4. Was there a project jQuery made suddenly possible?
  5. What did you stop hand-coding, and did you miss it?
  6. What is the trade-off when the tools get easier?
  7. How do you decide when a tool is helping versus hiding the craft?
05-06
Designing Through a Downturn✓ written7 questions
The recession reaching your clients; doing more with less.
  1. When did the 2008 crash actually reach your clients?
  2. What did fear do to the kind of work people asked for?
  3. How did you do more with less that year?
  4. Did you lose work, or change what you offered?
  5. What did a downturn reveal about which clients to keep?
  6. What did you learn about money and design in 2008?
  7. What from that year still shapes how you price and scope?
08-12
There's an App for That✓ written7 questions
The App Store opening; did you see apps coming, or bet on the web?
  1. Where were you when the App Store opened?
  2. Did you believe apps were the future, or a passing fad?
  3. Did you build, or wish you had built, something for it?
  4. What did the App Store change about what clients expected?
  5. What did you bet on instead, and were you right?
  6. What did the native versus web argument feel like then?
  7. What does that moment teach about which platforms to chase?
10-21
When Budgets Vanish, Restraint Wins✓ written7 questions
Clients slashing scope; restraint as necessity before it was philosophy.
  1. What did a client cutting scope in half teach you?
  2. When did restraint stop being a constraint and start being a philosophy?
  3. What did you cut that the project was genuinely better without?
  4. How did you protect quality with almost no budget?
  5. Did clients trust you more or less when you offered them less?
  6. What is the real difference between cheap and lean?
  7. How did 2008 plant the seed of telling clients what they do not need?
12-16
The Web Grew Up This Year✓ written7 questions
How the crisis matured the web and your work.
  1. How had the crisis matured the web by the end of the year?
  2. What grew up in you as a designer that year?
  3. What did you stop tolerating in your own work?
  4. Who survived the downturn, and why?
  5. What did clients finally start to value?
  6. What did you build at the end of 2008 that you were proud of?
  7. What did the hardest year so far give you?
2009
02-10
Twitter and the Art of 140 Characters✓ written7 questions
Brevity as design; what 140 characters taught you about words.
  1. When did you start using Twitter, and what hooked you?
  2. What did 140 characters teach you about words?
  3. How did that brevity change your design writing?
  4. What is the real discipline of saying less?
  5. Did the constraint make you more creative, or less?
  6. What is lost when there are no limits at all?
  7. How does fewer words, more signal trace back to here?
04-14
An Ad Agency Inside a Hospital✓ written7 questions
Covenant Health: turning the AV department into a creative agency, the Caritas to Covenant rebrand, fourteen facilities, designing for frightening days.
  1. What made you walk into an AV department and decide to build an agency out of it?
  2. Who was the vice president of communications ally, and how did you win them over?
  3. What did the Caritas to Covenant rebrand actually involve, and what was hardest?
  4. What is different about designing for fourteen facilities at once?
  5. What did designing for healthcare, for people on frightening days, teach you?
  6. What did building a lasting department teach you that a single project never could?
  7. What of that Creative Services Department still lives today, and how does it feel?
06-23
Less, But Better7 questions
Discovering restraint as a movement; the influences that shaped you.
  1. When did less, but better first truly click for you?
  2. Whose work shaped your sense of restraint?
  3. What did you strip out of your own work that year?
  4. Is minimalism about taste, or about respect for the person using it?
  5. What is the hardest thing to leave out?
  6. When does less become too little?
  7. How is your restraint different from plain minimalism?
09-15
The Mobile Web Is Not a Smaller Desk7 questions
Early mobile projects; the lessons that stuck.
  1. What was your first real mobile project?
  2. What did designers keep getting wrong about small screens?
  3. What did the phone force you to finally confront?
  4. What did you have to throw away from desktop thinking?
  5. What surprised you about how people actually used mobile?
  6. What did you predict back then that came true?
  7. How did mobile sharpen your sense of the one thing that matters?
11-24
Clients Are People, Especially When Money Is Tight7 questions
A hard client story from the downturn; how trust was won or lost.
  1. Tell me about a hard client from the recession years.
  2. What did the money pressure do to that relationship?
  3. How did you win, or lose, their trust?
  4. What did you learn about people under real stress?
  5. When did honesty cost you, and when did it pay off?
  6. What do you do differently with anxious clients now?
  7. What is the human lesson sitting under all the design?
2010
02-16
Designing for a Screen That Doesn't Exist Yet7 questions
Anticipating the tablet; the in-between screen nobody had designed for.
  1. What did you sense was coming before the iPad arrived?
  2. How do you design for something that does not exist yet?
  3. What did the in-between screen threaten, and what did it promise?
  4. Did you prepare for it, or get caught off guard?
  5. What is it like to work right on the edge of a shift?
  6. What did you guess wrong about tablets?
  7. How do you stay ready for the next unknown screen?
04-13
The iPad Changes the Question7 questions
The iPad arriving; the new screen between phone and desk.
  1. Where were you when the iPad launched?
  2. What new question did it force into your work?
  3. What did clients suddenly want once they held one?
  4. What did you build for it, or wish you had?
  5. Did it live up to the hype for the work you do?
  6. What did the iPad reveal about touch and intimacy with a screen?
  7. What did that middle screen teach you that stuck?
06-08
Responsive7 questions
First encountering responsive design; did it click immediately or scare you?
  1. When did you first read about responsive design?
  2. Did it click immediately, or did it scare you?
  3. What was your very first responsive build like?
  4. What did it break about your old way of working?
  5. What did clients understand, or not, about the word responsive?
  6. What did it permanently change about your process?
  7. Why was responsive more than just a technique?
09-21
The Municipal Project7 questions
Your city/municipal work, which project, what scale, what it taught you about serving the public.
  1. Which municipal project was this, and what exactly was your role?
  2. What was the scale of it, and when did that scale hit you?
  3. What is different about designing for citizens versus customers?
  4. What was the hardest constraint of public-sector work?
  5. Who did you serve that you would never actually meet?
  6. What went wrong, and how did you handle it at that scale?
  7. What did serving the public teach you about responsibility?
11-30
Serving a Million People7 questions
Designing for citizens versus customers; the scale of a city's digital front door.
  1. What does it feel like to design something a million people use?
  2. What kept you up at night on that work?
  3. How do you make something that vast feel simple?
  4. What is the difference between a feature and a public service?
  5. What did you remove that the organisation wanted to keep?
  6. What did a single citizen's complaint teach you?
  7. How does that scale shape how you treat a small client now?
2011
02-15
Mobile First7 questions
Flipping your process to design the small screen first; the pushback.
  1. When did mobile first stop being a slogan and become how you actually worked?
  2. What did designing the small screen first force you to decide earlier?
  3. What pushback did you get from clients or other designers?
  4. What was a project where mobile first genuinely changed the outcome?
  5. What did you used to put on a page that mobile first killed for good?
  6. What did this teach you about priorities, on a screen and off it?
  7. How does mobile first connect to your whole philosophy of restraint?
04-19
The Grid Got Fluid7 questions
Letting go of fixed widths; the mental shift to fluid layout.
  1. What did letting go of fixed widths feel like?
  2. What was hard about thinking in fluid proportions instead of pixels?
  3. What broke the first time you built something truly fluid?
  4. What did the fluid grid teach you about control versus trust?
  5. Did clients understand why their site could not be one fixed thing?
  6. What did you gain once you stopped fighting the browser?
  7. How is a fluid grid like designing for a future you cannot see?
07-26
A Photo App Just Out-Designed Us All7 questions
What Instagram's simplicity taught you about doing one thing well.
  1. When did you first use Instagram, and what struck you about it?
  2. What did a photo app teach you that a design tool never had?
  3. What is the power of an app that does one thing beautifully?
  4. Did it make you rethink anything in your own work?
  5. What did its constraints get right that feature-heavy apps got wrong?
  6. What did you envy about that simplicity?
  7. How does doing one thing well show up in how you build now?
09-13
Wayfinding for the Web7 questions
Your signage roots applied to web navigation; getting people un-lost.
  1. How did your signage and wayfinding roots feed your web navigation?
  2. What is the same about getting a person un-lost on a runway and on a website?
  3. What was a navigation problem you solved using a physical-world instinct?
  4. What do most websites get wrong about helping people find their way?
  5. When is the best navigation the one a person never notices?
  6. What did the track teach you about guiding a crowd?
  7. How do you design a path rather than a menu?
11-29
The Healthcare Years Begin7 questions
Your healthcare work, the org, what you built, the weight of designing for patients.
  1. Which healthcare organisation was this, and how did you come to the work?
  2. What did you actually build, a portal, wayfinding, a system?
  3. What is different about designing for patients rather than customers?
  4. What weight did you feel designing for people in fear or pain?
  5. What was the hardest constraint in healthcare work?
  6. What did a real patient story teach you?
  7. What did that world give you that you carry into everything now?
2012
02-14
Retina Changed My Pixels7 questions
Designing for retina; SVG and the death of the 1x image.
  1. What did designing for retina screens change overnight?
  2. What did you have to redo, and what did you learn doing it?
  3. Why did suddenly-sharp pixels matter so much to you?
  4. What did SVG and resolution independence open up?
  5. What did you stop doing the day the 1x image died?
  6. What is the craft lesson hiding in caring about a single pixel?
  7. How does that obsession with sharpness show up in your work today?
04-24
The Slow Death of Flash7 questions
Letting go of Flash; what was lost and gained.
  1. When did you know Flash was truly finished?
  2. What did you lose that you actually mourned?
  3. What was the last Flash thing you ever built?
  4. What did the open web gain when Flash fell?
  5. What did you have to tell clients who still wanted it?
  6. What is the lesson about betting your craft on one company's tool?
  7. What did the death of Flash teach you about durability?
07-17
Flat Is Coming7 questions
Sensing the turn away from skeuomorphism; your early read on flat.
  1. When did you first sense the turn away from skeuomorphism?
  2. What did you find honest about flat design?
  3. What did you worry flat would lose?
  4. What was a project where you went flat early?
  5. What did clients think when you took away the shadows and textures?
  6. Was flat a real philosophy, or just the next fashion?
  7. What did this taste shift teach you about trends and conviction?
09-25
Designing for Anxious Moments7 questions
Designing for people in fear or pain; warmth and clarity under stress.
  1. Tell me about designing for an anxious moment, who was the person?
  2. How do warmth and clarity work together under stress?
  3. What did you remove because fear leaves no room for clutter?
  4. What did a patient or family member teach you about real needs?
  5. When is design genuinely an act of care?
  6. What is the cost of getting it wrong in healthcare?
  7. How does designing for fear change how you design for everything?
11-20
Seven Years In7 questions
Seven years in, what you had unlearned.
  1. Seven years in, what had you finally unlearned?
  2. What were you proud of, and quietly tired of?
  3. Who or what had shaped you most by 2012?
  4. What did you believe about the work that you no longer did?
  5. What were you still chasing?
  6. What habit from year seven still defines you?
  7. What would you tell yourself heading into the next stretch?
2013
02-12
The Long Scroll7 questions
The shift to long, scrolling pages; when it helped and when it was just fashion.
  1. When did long, scrolling pages start to make sense to you?
  2. What did the long scroll let you do that the old way could not?
  3. When was a long page just fashion rather than function?
  4. What did parallax promise, and where did it go wrong?
  5. What was a scrolling story you were proud of?
  6. How do you decide when to make someone scroll versus click?
  7. What did this teach you about pacing and rhythm in a page?
06-18
iOS 7 and the End of Skeuomorphism7 questions
The day Apple went flat; your reaction.
  1. Where were you when Apple went flat with iOS 7?
  2. What was your honest first reaction?
  3. What did it validate, or contradict, in your own taste?
  4. How did clients respond to the whole world going flat at once?
  5. What did the industry overcorrect on?
  6. What is the difference between following Apple and having your own taste?
  7. What did that moment teach you about who sets the trends?
08-27
Content Is the Design7 questions
Realising the words come first; designing around real content, not lorem ipsum.
  1. When did you realise the words come before the design?
  2. What was a project that fell apart for lack of real content?
  3. What changed when you started designing around true content, not lorem ipsum?
  4. How do you get clients to take their own words seriously?
  5. What is the relationship between writing and design for you?
  6. Why is content the thing most projects skip and most regret?
  7. How does content-first thinking show up in your work now?
10-15
Downtown Is Changing7 questions
The downtown revitalization branding work; shaping how a city sees itself.
  1. What was your role in the downtown revitalization work?
  2. What does it mean to shape how a city sees itself?
  3. What was the hardest part of branding a place, not a product?
  4. Who were you really designing for, and who pushed back?
  5. What did you want a citizen to feel walking through that change?
  6. What is the responsibility of designing something meant to last?
  7. What did that civic work teach you about permanence?
12-10
Branding a Place, Not a Product7 questions
How branding a place differs from branding a product; the responsibility of it.
  1. What is fundamentally different about branding a place versus a product?
  2. How do you find the truth of a place that already exists?
  3. What did you have to listen for before you designed anything?
  4. What was a place-branding decision you fought for?
  5. What is the danger of imposing a brand on a community?
  6. When does place branding become honest rather than spin?
  7. What did this teach you about humility in the work?
2014
02-25
Pitching a City7 questions
Branding Edmonton's Commonwealth Games bid; designing a pitch that sells a whole city.
  1. What was it like branding Edmonton's Commonwealth Games bid?
  2. How do you design a pitch that has to sell an entire city?
  3. Who was the audience you were really trying to move?
  4. What was the emotional core you built the bid around?
  5. What was the hardest deadline or constraint on that work?
  6. What did pitching at that scale teach you about persuasion?
  7. What did you pour into it that few people will ever see?
05-20
Material Design and the Return of Rules7 questions
Material arriving; your take on systematized design with real rules.
  1. What was your read on Material Design when it landed?
  2. What did you like about design with real, stated rules?
  3. What did systematized design threaten to flatten?
  4. Did you adopt it, resist it, or borrow from it?
  5. What is the value of a shared language across a whole system?
  6. When do rules free you, and when do they cage you?
  7. How did Material shape how you think about systems now?
07-29
The Brand Gap7 questions
The gap between strategy and execution; fusing the two under one judgment.
  1. What is the gap between brand strategy and brand execution?
  2. When did you decide to fuse the two under one judgment?
  3. What goes wrong when strategy and the build are handed to different teams?
  4. What was a project where holding both made all the difference?
  5. Why do most studios gesture at strategy but staff it out?
  6. What does it take to do both well in one head?
  7. How is this fusion your real competitive edge?
09-30
Designing Something That Shapes a Decade7 questions
Designing work meant to last ten years; the pressure of permanence.
  1. What is it like designing something meant to last ten years?
  2. What changes when permanence is the brief?
  3. How do you design for a future you cannot fully picture?
  4. What did you deliberately leave timeless, and what did you let date?
  5. What was the pressure of work that a city would live with?
  6. What did long-horizon work teach you about restraint?
  7. What did you build then that you would still stand behind today?
11-18
Almost a Decade In7 questions
Nearly ten years; what you now refuse to compromise on.
  1. Nearly ten years in, what would you no longer compromise on?
  2. What did you finally feel certain about?
  3. What were you still wrestling with?
  4. Who had become your measure of good work?
  5. What did a decade of redesigns teach you about what never changes?
  6. What did you want the next ten years to be about?
  7. What would you tell the version of you who just graduated?
2015
02-17
Sometimes the Work Doesn't Win7 questions
Handling work that does not ship; grace when a project ends.
  1. How did it feel when the Commonwealth Games bid was withdrawn?
  2. What do you do with work that pours out of you and then never ships?
  3. What did you learn from a project that ended before it lived?
  4. How do you find grace when the decision is out of your hands?
  5. What did you keep from that work even though it went nowhere?
  6. What does unshipped work teach you that shipped work cannot?
  7. How do you talk to a client about a project that will not win?
04-21
Mobilegeddon7 questions
The day Google made mobile a ranking factor; clients suddenly listening.
  1. What was the day Google made mobile a ranking factor like?
  2. Did clients who ignored you suddenly start listening?
  3. What did Mobilegeddon prove that you had been saying for years?
  4. What is it like to be right a few years too early?
  5. What did the panic reveal about how businesses treat the web?
  6. What did you fix in a hurry for clients that spring?
  7. What did this teach you about when people finally change?
06-23
The Craft of the Small-Business Brand7 questions
A small local brand you built, the salon, the beef, the vines. Pick one and tell the story.
  1. Pick one small local brand you built, the salon, the beef, the vines, and tell its story.
  2. What did that owner care about that no template would understand?
  3. What was the truth of their business you had to find first?
  4. What was the detail you sweated that made it theirs?
  5. What did it feel like to see your work out in the real world?
  6. What is different about branding a small business versus a big one?
  7. What did that owner teach you about craft and pride?
09-15
Design Systems Before They Had a Name7 questions
Building reusable systems before the industry had the vocabulary.
  1. What were you building before the industry had the words design system?
  2. What problem were you actually solving with reusable parts?
  3. What did systematizing your own work change?
  4. When does a system help, and when does it make everything the same?
  5. What did you intuit that the industry later formalised?
  6. What is the tension between a system and a soul?
  7. How do you keep a system alive rather than mechanical?
11-24
Ten Years7 questions
A full decade, the through-line you finally saw.
  1. A full decade in, what through line did you finally see?
  2. What had stayed true from the racetrack to now?
  3. What had completely changed about you and the work?
  4. What were you proudest of across ten years?
  5. What regret or wrong turn taught you the most?
  6. What did ten years earn you that you could not have rushed?
  7. What did you want the next decade to be?
2016
02-23
Everything Became a Card7 questions
The card pattern taking over; useful or lazy?
  1. When did everything start becoming a card?
  2. What did the card pattern solve, and what did it flatten?
  3. Was it useful, or just an easy answer everyone reached for?
  4. What did you do to keep card-based work from looking generic?
  5. What does a trend like this reveal about how designers borrow?
  6. When is a pattern a tool, and when is it a crutch?
  7. How do you use a common pattern and still make it yours?
04-19
The Chatbot Year7 questions
The first chatbot wave; what you believed and what you doubted.
  1. What did you make of the first big chatbot wave?
  2. What did you believe about conversational interfaces, and what did you doubt?
  3. Did you build anything with it, and how did it go?
  4. What did the hype get wrong about how people want to interact?
  5. What did it get right that came back later?
  6. What is the difference between a real interface and a gimmick?
  7. What did that wave teach you about chasing the new?
07-12
Branding Beef and Wine7 questions
The food and drink brands; designing for a shelf and a story.
  1. Tell me about the food or drink brands, the beef, the wine, the packaging.
  2. What is different about designing for a physical shelf and a story?
  3. What did the owner want a customer to feel picking it up?
  4. What was the detail on the package you fought for?
  5. What did designing something you could hold teach you?
  6. How do brand, taste, and appetite come together in that work?
  7. What did those makers teach you about their craft and yours?
09-27
The Speed Obsession7 questions
When 'fast' became a feature; your view on speed versus substance.
  1. When did fast become a feature everyone suddenly demanded?
  2. What is the honest relationship between speed and substance?
  3. What did the obsession with performance scores get right?
  4. Where did chasing speed make the work worse?
  5. What did you do to make something both fast and worth arriving at?
  6. Is a fast empty page better than a slower meaningful one?
  7. How do you hold speed and depth together now?
11-22
Agency, In-House, or Alone7 questions
Weighing agency life versus going solo; what pulled you each way.
  1. What pulled you toward agency life, and what pulled you away?
  2. What did you weigh between in-house, agency, and going solo?
  3. What did you fear about being on your own for good?
  4. What did the agency model get wrong for someone like you?
  5. What did you want that only working alone could give you?
  6. When did you know which path was yours?
  7. What did wrestling with that choice teach you about how you work best?
2017
02-21
Design Tokens7 questions
Tokenising a design language; the engineer and the designer speaking one tongue.
  1. What problem were design tokens actually solving for you?
  2. When did you start naming your design decisions as a system?
  3. What changed when the designer and the engineer shared one language?
  4. What was a project where tokens saved you?
  5. What is the risk of systematizing too early or too hard?
  6. How do tokens connect taste to code without killing either?
  7. What did this teach you about the seam between design and build?
04-18
Sketch, and Then This Thing Called Figma7 questions
Your tools in 2017; the first time you tried Figma in the browser.
  1. What was your toolkit in 2017, and what did Sketch give you?
  2. What was the first time you opened Figma in a browser like?
  3. What did you not believe a browser tool could do, until it did?
  4. What did the shift to Figma change about how you worked with others?
  5. What did you lose or miss from the old tools?
  6. How do you decide when to switch the tools you build with?
  7. What does this say about betting on where the craft is heading?
07-25
Branding a Crypto Ecosystem7 questions
The crypto branding work; the wild energy of the ICO days.
  1. How did you end up branding a crypto ecosystem?
  2. What was the energy of the ICO days actually like?
  3. What did you believe about it at the time, honestly?
  4. What was hard about branding something so new and so hyped?
  5. What did you build that you were genuinely proud of?
  6. What did the wild speculation teach you about substance?
  7. What would you tell a client riding a hype wave like that?
09-19
Eighty Coins and a Brand to Hold Them7 questions
Designing a brand to contain dozens of moving parts; order in chaos.
  1. What does it take to brand something with dozens of moving parts?
  2. How do you create order out of that kind of chaos?
  3. What was the single idea that held the whole thing together?
  4. What was the hardest part of designing a system that big?
  5. What did you have to leave out to keep it coherent?
  6. What did this teach you about structure and restraint at scale?
  7. What from that work shows up in how you organise anything now?
11-28
The Solo Operator Stirs7 questions
The first serious thought of building something that was only yours.
  1. When did the first serious thought of building your own thing arrive?
  2. What were you tired of, or hungry for, by late 2017?
  3. What did you imagine a practice that was only yours could be?
  4. What scared you about it?
  5. What did you already know you would do differently?
  6. What were you waiting for before you committed?
  7. What did that early stirring tell you about what you really wanted?
2018
02-20
Variable Fonts Finally Arrived7 questions
Type that flexes; a small revolution most people missed.
  1. What did variable fonts open up that excited you?
  2. Why did most people miss this quiet revolution?
  3. What was a project where flexible type changed the work?
  4. Why does type keep being the thing you care about most?
  5. What does type that flexes teach about design that flexes?
  6. What did you do with this that few others bothered to?
  7. How does caring about something most overlook define your craft?
05-22
GDPR and the Return of Honesty7 questions
Privacy law forcing honest design; your view on consent and respect.
  1. What did GDPR force into your work in 2018?
  2. Why did you welcome a privacy law that others resented?
  3. What does honest design around consent actually look like?
  4. What dark habits did the industry have to give up?
  5. What did you already do that the law caught up to?
  6. What is the relationship between privacy and respect?
  7. How does this connect to clients owning their own data?
07-17
Dark Patterns and the Cost of Tricks7 questions
Refusing to design manipulation; a time you talked a client out of a trick.
  1. When did you first refuse to design a dark pattern?
  2. Tell me about a time you talked a client out of a trick.
  3. What is the real cost of manipulating a user into something?
  4. What did saying no to a tactic cost you, or earn you?
  5. Where is the line between persuasion and manipulation?
  6. Why is restraint here a moral choice, not just a taste one?
  7. How does refusing tricks build the trust your whole brand runs on?
09-25
Figma Killed the Handoff7 questions
Real-time collaboration changing how you work with developers and clients.
  1. What did real-time collaboration change about working with developers?
  2. What did the death of the handoff feel like?
  3. What friction disappeared, and what new friction appeared?
  4. How did clients react to watching the work happen live?
  5. What did you gain when design stopped being thrown over a wall?
  6. What is lost when everyone can see everything all the time?
  7. How did this reshape how you collaborate now?
11-27
Designing Like You Mean It7 questions
Conviction in the work; what you stopped apologising for.
  1. What did designing with conviction start to mean to you?
  2. What did you stop apologising for in your work?
  3. When did you start trusting your own judgment fully?
  4. What was a project where you held your ground and were right?
  5. What is the difference between confidence and bravado?
  6. What did meaning it change about how clients received the work?
  7. What did 2018 settle in you as a designer?
2019
02-19
Accessibility Is Not Optional7 questions
When accessibility became central to your craft, not an afterthought.
  1. When did accessibility move to the centre of your craft?
  2. What was the project or person that made it real for you?
  3. What did you have to relearn to design for everyone?
  4. What is the most common thing designers get wrong about access?
  5. Why is accessibility a form of respect, not a checklist?
  6. What did designing for constraints teach you about design itself?
  7. How does it shape everything you build now?
04-23
Working With the World7 questions
Your Toptal/global era, clients across time zones, what it taught you about working anywhere.
  1. What was your Toptal and global-client era actually like?
  2. What did working across time zones teach you?
  3. Who was a client from across the world you still remember?
  4. What did you learn about working anywhere, for anyone?
  5. What is different about earning trust remotely?
  6. What did global work reveal about what is universal in good design?
  7. What did that era give you that local work never could?
06-25
Design Ops and the Machine of Making7 questions
Systematising your own practice; the operations behind the craft.
  1. What did systematizing your own practice change?
  2. What is the operations behind the craft that nobody sees?
  3. What did you automate or streamline first, and why?
  4. What did design ops let you stop worrying about?
  5. Where does process help, and where does it strangle the work?
  6. How do you keep operations in service of the craft?
  7. How did this become the seed of how you run things now?
09-17
The Polished Sameness of SaaS7 questions
First noticing every SaaS site looked the same; the seed of a bigger idea.
  1. When did you first notice every SaaS site looked the same?
  2. What did that uniform, polished sameness do to you?
  3. What was the seed of a bigger idea hiding in that observation?
  4. Why did everyone arrive at the identical look?
  5. What did you want to do differently, even then?
  6. What is the cost of a whole industry looking alike?
  7. How does this connect to your sameness thesis years later?
11-26
Remote Before It Was Required7 questions
Working remotely before the world had to; the discipline it took.
  1. What did working remotely before it was required take?
  2. What discipline did remote work demand of you?
  3. What did you figure out that the world would soon need?
  4. What did you miss about being in a room with people?
  5. What did distance teach you about trust and communication?
  6. What were you doing in late 2019 that 2020 would make universal?
  7. What did being early to remote give you?
2020
03-17
The Week Everything Went Remote7 questions
COVID arriving; your work and your clients overnight.
  1. Where were you the week everything went remote?
  2. What happened to your work and your clients overnight?
  3. What did you scramble to help people with first?
  4. What did fear do to what businesses suddenly needed?
  5. What did you feel watching the world stop?
  6. What did that week change in you, for good?
  7. What did you learn about what is essential when everything pauses?
05-19
Every Business Needs a Storefront Now7 questions
The rush to sell online; helping owners who had never needed a website before.
  1. What was the rush to sell online actually like for your clients?
  2. Who needed a website that had never needed one before?
  3. What did you build fast that spring, and how did it hold up?
  4. What did the e-commerce surge reveal about who was ready?
  5. What did desperation teach you about helping people quickly?
  6. What did you have to talk people out of, even in a panic?
  7. What did 2020 prove about the web as a lifeline?
07-21
Designing for a Year Indoors7 questions
What a year indoors changed about how people use the web, and about you.
  1. What did a year mostly indoors change about how people use the web?
  2. What did it change about you?
  3. What did people suddenly want from the screens in their lives?
  4. What kind of work felt meaningful in that strange year?
  5. What did you make that you were proud of during lockdown?
  6. What did the quiet give you that the noise never did?
  7. What did designing for a world indoors teach you?
09-29
The Great Acceleration7 questions
Ten years of digital change in one; who adapted and who did not.
  1. What did ten years of digital change compressed into one feel like?
  2. Who adapted, and who did not, and why?
  3. What did the great acceleration expose about businesses?
  4. What did you help a client survive that year?
  5. What did speed of change cost, even when it was necessary?
  6. What did you learn about resilience from that period?
  7. What did the acceleration leave permanently changed?
11-24
What the Pandemic Taught Me About Essentials7 questions
Stripping everything to essentials; what truly mattered when it all stopped.
  1. What did the pandemic strip down to essentials for you?
  2. What did you realise truly mattered when everything stopped?
  3. What did you let go of that you do not miss?
  4. What did clients finally see as essential versus nice to have?
  5. How did that clarity change your work?
  6. What is the gift hidden in a year that took so much?
  7. How does that lesson of essentials shape your restraint now?
2021
02-16
The Tyranny of the Speed Score7 questions
Google scoring speed; the good and the obsessive sides of it.
  1. What did Google scoring your speed do to the work?
  2. What is good about Core Web Vitals, and what is obsessive?
  3. Where did chasing a green score make the work worse?
  4. How do you serve a metric without serving only the metric?
  5. What did clients misunderstand about speed scores?
  6. What is the difference between fast and good?
  7. How do you keep judgment above the number?
04-20
No-Code and the Democratization of Building7 questions
No-code tools arriving; threat, gift, or both for a craftsperson?
  1. What did the rise of no-code make you feel, as a craftsperson?
  2. Is no-code a threat, a gift, or both?
  3. What can no-code genuinely do, and where does it fall short?
  4. What did it change about who can build things?
  5. What did democratized building teach you about your own value?
  6. Where does taste matter more when the building gets easy?
  7. How do you think about tools that lower the barrier?
07-27
The NFT Year7 questions
The web3 wave; what you engaged with and what you sat out.
  1. What did you make of the NFT and web3 wave?
  2. What did you engage with, and what did you deliberately sit out?
  3. What did the hype get right, and where did it lose its way?
  4. What did you believe about ownership and the web then?
  5. What did the speculation teach you about value and substance?
  6. What would you have told a client desperate to jump in?
  7. What survived that wave that was actually worth keeping?
09-21
Owning Versus Renting7 questions
The idea crystallising: build an asset clients own, not a thing they rent.
  1. When did owning versus renting crystallise as your idea?
  2. What is the real difference between a platform and an asset?
  3. What did you see clients lose by renting their presence?
  4. What does it mean for a client to truly own their site and data?
  5. What is the danger of building your business on someone else's land?
  6. Why does ownership matter more the longer you run a business?
  7. How did this become a pillar of how you sell your work?
11-23
The Great Resignation Was a Design Problem7 questions
People rethinking work; what it said about meaning and craft.
  1. Why do you see the great resignation as a design problem?
  2. What were people really walking away from?
  3. What did that moment reveal about meaning in work?
  4. What did it make you reconsider about your own path?
  5. What is the connection between craft, autonomy, and staying?
  6. What did people seem to be searching for instead?
  7. What did that year teach you about building a life around the work?
2022
02-22
Web3 Cools, the Real Work Remains7 questions
When the speculative noise faded; returning to substance.
  1. When the web3 noise faded, what real work was left standing?
  2. What did you feel watching a hype cycle deflate?
  3. What had you held onto while everyone else chased the speculation?
  4. What did the quiet after the hype let you see clearly?
  5. What did you return your attention to in early 2022?
  6. What does a deflating bubble teach about substance?
  7. What did you want to build once the noise was gone?
05-17
A Machine Drew a Picture This Spring7 questions
First reaction to AI image tools; wonder, worry, or both.
  1. Where were you the first time a machine drew you a picture?
  2. What was your honest first reaction, wonder, worry, or both?
  3. What did you immediately understand about what was coming?
  4. What did you try to make with it that first spring?
  5. What did it threaten, and what did it promise, for your craft?
  6. What did you get wrong in your first read of it?
  7. What did that moment tell you about the years ahead?
08-30
The Tools Are Learning to See7 questions
Watching the tools cross a line; what you thought it meant for the craft.
  1. When did you sense the tools had crossed a real line?
  2. What did it mean to you that machines were learning to see?
  3. What did you start doing differently in your work?
  4. What did you refuse to hand to the machine, even then?
  5. What did the speed of it all make you feel?
  6. What did you believe taste would be worth in this new world?
  7. What did you want to protect as the tools got powerful?
11-30
Something Happened in November7 questions
The day you first used ChatGPT; where you were and what you felt.
  1. Where were you the first time you used ChatGPT?
  2. What did you feel in those first few minutes?
  3. Who did you tell, and did they understand?
  4. What did you immediately see that others missed?
  5. What did you start experimenting with right away?
  6. What did you decide you would never let it do for you?
  7. What did that November tell you about the decade ahead?
12-20
The Year the Ground Shifted7 questions
Closing a year that changed everything; your resolve heading into it.
  1. Why did 2022 feel like the year the ground shifted?
  2. What had changed for good by the end of it?
  3. What were you most excited about, and most wary of?
  4. What did you resolve heading into the AI years?
  5. What did you want to carry forward, unchanged?
  6. What did you let go of as the world sped up?
  7. What did you promise yourself the machines would not take?
2023
02-21
Everyone Is Talking to a Machine Now7 questions
The AI gold rush; how you decided to use it without losing yourself.
  1. What was the AI gold rush of early 2023 like to live through?
  2. How did you decide to use these tools without losing yourself?
  3. What did the frenzy get right, and where did it lose its head?
  4. What did clients suddenly want, and what did they fear?
  5. What did you refuse to do, even as everyone rushed in?
  6. What did the rush reveal about people and shiny new things?
  7. What did you decide your role would be in this new world?
04-25
AI Will Not Replace Taste7 questions
Your early conviction that judgment, not output, is the value.
  1. When did you become certain AI would not replace taste?
  2. What is the difference between making something and judging it?
  3. What did you watch the machine do well, and do badly?
  4. Why does judgment become more valuable as output gets cheap?
  5. What did you tell anxious designers that year?
  6. What did you stake your own future on?
  7. Why is taste the one thing that cannot be automated?
07-18
The Honest Middle7 questions
The gap between DIY platforms and expensive agencies; the space you decided to own.
  1. When did the honest middle become clear to you as your place?
  2. What is the gap between cheap platforms and expensive agencies?
  3. Who is the owner that nobody in that gap is serving?
  4. What did you decide to offer that no one else would?
  5. Why is protecting the client over your margin the whole brand?
  6. What did claiming that middle cost you, and earn you?
  7. Why could no competitor easily follow you there?
09-26
Automating the Mundane7 questions
The first automation that gave you real hours back; the principle it revealed.
  1. What was the first automation that gave you real hours back?
  2. What did you do with the time it returned?
  3. What is the principle that automation revealed to you?
  4. What did you decide should never be automated?
  5. How do you choose what to hand to a machine?
  6. What did clients gain when you took the drudgery away?
  7. How did this become the greenhouse idea you live by now?
11-28
One Person, Every Discipline7 questions
The solo-operator thesis taking shape; brand, build, and automate under one judgment.
  1. When did one person, every discipline become your real thesis?
  2. What does it take to hold brand, build, and automation in one head?
  3. What did you stop outsourcing, and why?
  4. What is gained when a single judgment runs the whole project?
  5. What is the hardest part of being the only one accountable?
  6. Why is this the right shape for the work right now?
  7. What did committing to that fully change for you?
2024
02-20
The Studio That Ships Like Ten7 questions
How one person, with the right tools, now matches a whole team.
  1. What does it mean that one person can now ship like ten?
  2. What did the right tools let you do that a whole team used to?
  3. Where do you still hit the limits of being one person?
  4. What did this change about who you compete with?
  5. What did clients gain from a studio with no overhead or committee?
  6. What is the catch nobody talks about in the solo studio?
  7. What did proving this to yourself feel like?
04-23
When the Machine Can Build, Judgment Is the Job7 questions
Production becoming cheap; taste becoming the product.
  1. Once the machine can build, what exactly is the job?
  2. What did cheap production do to the value of judgment?
  3. What did you stop charging for, and start charging for?
  4. What is the difference between a builder and a master now?
  5. What did this shift threaten, and what did it free?
  6. How do you explain your value when anyone can make anything?
  7. Why does this make taste the whole product?
07-16
Replacing the Agency, the Dev Team, and the IT Desk7 questions
The day you could honestly say you replace all three; how you got there.
  1. When could you honestly say you replace the agency, the dev team, and the IT desk?
  2. How did you get to where all three were true at once?
  3. What did each of those roles teach you along the way?
  4. What is the catch, and how do you handle it honestly?
  5. What does an owner gain by having one accountable mind instead of three vendors?
  6. What did it take to be trusted with all of it?
  7. Why is this the offer the moment was waiting for?
09-24
Sovereignty7 questions
What it means for a client to truly own their site, content, and data.
  1. What does sovereignty mean to you in this work?
  2. What does it really mean for a client to own their site, content, and data?
  3. What did you watch clients lose by renting everything?
  4. Why does ownership matter more the longer someone is in business?
  5. What is the danger of building on land you do not control?
  6. How do you build something a client keeps for good?
  7. Why is owned, not rented, a promise worth making?
11-26
The Empire Takes Shape7 questions
Naming and building Ellis Empire; many holdings, one standard.
  1. When did Ellis Empire get its name, and why that word?
  2. What does many holdings, one standard mean to you?
  3. What were you committing to by naming it?
  4. What did building your own thing finally feel like?
  5. What standard did you refuse to lower as it grew?
  6. What did you want the Empire to mean to a client?
  7. What did naming it change about how you worked?
2025
02-18
The First Time I Noticed the Sameness7 questions
When you first saw AI flattening the web into one template; the worry and the opportunity.
  1. When did you first see AI flattening the whole web into one template?
  2. What did that sameness do to you as a craftsperson?
  3. What was the worry, and what was the opportunity in it?
  4. Why did everyone arrive at the identical look so fast?
  5. What did you decide to do differently because of it?
  6. What is the cost to a business of disappearing into the herd?
  7. How did this become the heart of your flagship thinking?
04-22
The Greenhouse Year7 questions
When the greenhouse and the work started feeling like the same idea.
  1. When did the greenhouse and the work start to feel like the same idea?
  2. What does the land give you that the screen never can?
  3. How did tending real growing things change how you build systems?
  4. What is the harmony you found between nature and the machine?
  5. What did a hard season teach you about protection and patience?
  6. Why is the greenhouse the truest way you explain AI now?
  7. What did the homestead settle in you?
06-24
Restraint as a Business Model7 questions
Telling clients what they don't need as the core of the brand; why it builds loyalty.
  1. How did restraint become an actual business model for you?
  2. Why does telling clients what they do not need build loyalty?
  3. What did you watch happen when you protected a client over your margin?
  4. What is the long game that restraint plays?
  5. What did this posture cost you in the short term?
  6. Why can the everything-bundle sellers never copy this?
  7. What did living this prove to you?
09-23
Big-Brand Thinking, Built for the Business in Front of Me7 questions
Principal-led, studio-grade work at a reach a local owner can say yes to.
  1. What does big-brand thinking, built for the business in front of you mean?
  2. How do you bring studio-grade work to a local owner?
  3. What is the reach a small owner can actually say yes to?
  4. What did the big-budget world teach you that you bring to the small one?
  5. Why is principal-led work different from an agency's?
  6. Who is the owner you most love to work with, and why?
  7. What promise sits under all of it?
11-25
Twenty Years of Pages7 questions
Two decades and tens of thousands of pages; the smallest lesson at the end of it.
  1. Twenty years and tens of thousands of pages, what is the smallest lesson at the end of it?
  2. What has stayed true from the racetrack to now?
  3. What did all those pages teach you about what to leave out?
  4. What are you proudest of across two decades?
  5. What wrong turn taught you the most?
  6. What do you know now that you could not have rushed?
  7. What do you want the next twenty years to be?
2026
01-20
A New Year, A New Home7 questions
Launching the new site; what you wanted it to say without saying it.
  1. What did you want the new jonathanellis.ca to say without saying it?
  2. What did launching a new home feel like after all these years?
  3. What did you put on it, and what did you deliberately leave off?
  4. What were you trying to make a visitor feel in the first second?
  5. What did building your own site teach you that client work never did?
  6. What were you afraid of in putting it out there?
  7. What does this site represent that the old ones did not?
02-17
The Standard, Daily7 questions
Why you decided to publish consistently; the discipline of showing up.
  1. Why did you decide to publish consistently, every day?
  2. What is the discipline of showing up on the page?
  3. What were you afraid would happen, or not happen?
  4. What does daily writing ask of you?
  5. What do you hope a reader feels, finding you day after day?
  6. Why let the work pull, rather than ever asking for the follow?
  7. What does the standard, daily mean to you?
03-24
What I Talk Clients Out Of7 questions
A recent moment you protected a client over your own margin.
  1. What is a recent moment you protected a client over your own margin?
  2. What did you talk them out of, and how did they react?
  3. What did saying no cost you, and what did it earn you?
  4. Why is this the part of the work you are proudest of?
  5. How do you know when less is genuinely the right answer?
  6. What does an owner feel when you protect them?
  7. Why does honesty against your own interest build the deepest trust?
04-21
A Field of Sameness7 questions
The local field all saying the same thing; how you choose to stand apart.
  1. What does the Edmonton field look like to you right now?
  2. Why does it all sound the same, and what is the opening in that?
  3. How do you choose to stand apart without throwing shade?
  4. What is the one true thing you say that no competitor does?
  5. What did studying the field teach you about your own gap?
  6. Why is sameness the real competition, not any one rival?
  7. What do you want a local owner to feel finding you in that field?
05-26
Built for the Business in Front of Me7 questions
The promise you make to every owner; the bridge into the daily posts that follow.
  1. What is the promise you make to every owner who finds you?
  2. What does built for the business in front of me really mean?
  3. How do you keep big thinking and a small owner's reach in one offer?
  4. What is the bridge from this post into the daily ones that follow?
  5. What do you want this to set up for everything you publish next?
  6. Why is this the right note to stand on as you begin?
  7. What is the single thing you hope a reader carries away?
03

The Content Engine

One post a day, but the week has a shape. Seven lanes, seven registers · drawn from your real life: the studio, the land, the workshop, the music, the family. A reader never gets the same note twice.

Monday

The Essay

Considered, visionary

The long-form piece of the week, the idea everything else orbits. Cross-adapted to every platform across the days that follow.

e.g. Why Everything Looks the Same
Tuesday

The Craft

Precise, quietly proud

One principle of taste made concrete. A detail most people miss. Restraint shown, not preached, and often drawn from tuning a guitar or measuring a cut.

e.g. Why one real photograph beats ten stock ones.
Wednesday

From the Land & the Workshop

Warm, vulnerable, alive

The maker lane. Greenhouse and garden, the car in the driveway, the half-finished kitchen, a song at the end of the day, a nearly-five-year-old's questions, each fused with a lesson about systems, patience, problem-solving, or building. The emotional centre of the brand.

e.g. The Greenhouse and the Machine
Thursday

The Honest Take

Calm, candid, generous

What you do not need. Owning versus renting. The honest middle nobody serves. Truth told against short-term interest.

e.g. The thing I talk most clients out of.
Friday

Where It's Going

Curious, forward, never fearful

The near future of the work, AI as a tool under human judgment, the solo operator who ships like ten, the human-in-the-loop. Reflection, not prediction theatre.

e.g. Faster is not always better, the heresy of the moment.
Saturday

The Reply

Conversational, helpful

A real question answered plainly, from a comment, a client, a prospect. The most human, least polished day. Builds the sense of a person who actually replies.

e.g. Someone asked: do I really need a blog? The honest answer.
Sunday

The Quiet One

Still, luxurious

One line. One photograph, the land at dusk, the workshop, a single composed detail. No teaching. Just presence. The luxury signal: the brand that does not need to shout on the day everyone else is loud.

e.g. First light through the greenhouse glass, and six words.

Batch cadence

3 + 6 + 9 + 9 + 9 + 9 + 9 + 9 + 9 + 9 ≈ 81-90 posts over the next ninety days at one a day, the queue always running a few weeks ahead. The dated 90-day plan is generated to engine/content-calendar-90day.csv.

3delivered

Batch 0 · Flagships

The three identity-defining pieces. Posting today, Friday, Saturday. The voice is set here.

6next

Batch 1 · First week+

Six posts to complete the launch week across the lanes, refined to your interview answers.

9planned

Batch 2 · First nine

Nine posts. By now the cadence is felt and the voice is yours on the page.

9ongoing

Batch 3+ · Steady state

Nine per batch, always, about nine days of posting each. Every batch checked against the ledger so nothing repeats.

The 90-day plan

First three weeks shown; the flagships lead the launch (in green), then the weekly rhythm runs. The full 90-day dated plan is in engine/content-calendar-90day.csv.

Thu Jun 25
The Opener
F00 · How I Talk You Out of Working With Me
Fri Jun 26
The Essay
F01 · Why Everything Looks the Same
Sat Jun 27
From the Land & the Workshop
F02 · The Greenhouse and the Machine
Sun Jun 28
Field Notes
F03 · Twenty-Four Thousand Pages
Mon Jun 29
The Essay
The end of the brochure website, and the rise of the conduit.
Tue Jun 30
The Craft
Why one real photograph beats ten stock ones, and how to take the one.
Wed Jul 01
From the Land & the Workshop
What pruning taught me about cutting features.
Thu Jul 02
The Honest Take
The thing I talk most clients out of.
Fri Jul 03
Where It's Going
Faster is not always better, the heresy of the moment.
Sat Jul 04
The Reply
Someone asked: do I really need a blog? The honest answer.
Sun Jul 05
The Quiet One
First light through the greenhouse glass. Six words.
Mon Jul 06
The Essay
Taste is the last thing that cannot be automated.
Tue Jul 07
The Craft
The tyranny of the three-icon row, and what to put there instead.
Wed Jul 08
From the Land & the Workshop
Rebuilding a carburetor and refactoring a codebase are the same patience.
Thu Jul 09
The Honest Take
Rent versus own: the difference between a platform and an asset.
Fri Jul 10
Where It's Going
AI does not replace taste. It raises the price of having it.
Sat Jul 11
The Reply
A reader asked how I stay fast as one person. The real reason.
Sun Jul 12
The Quiet One
The studio at dusk, one green light on. Only the date.
Mon Jul 13
The Essay
Why the one-person studio is the right size for this decade.
Tue Jul 14
The Craft
White space is not empty. It is the most confident thing on the page.
Wed Jul 15
From the Land & the Workshop
My daughter asks why a hundred times a day. It made me a better designer.
04

The Topic Bank

The fuel. One-line seeds, by lane, drawn from your real life, the studio, the land, the workshop, the music, the family. Deep enough to run the full ninety days without repeating; we keep adding as your stories surface in the interviews. 98 seeds loaded.

The Essay

  • The end of the brochure website, and the rise of the conduit.
  • Taste is the last thing that cannot be automated.
  • Why the one-person studio is the right size for this decade.
  • The difference between a tool and a master: who is holding whom.
  • Restraint as a competitive advantage, not a style.
  • What twenty years of redesigns taught me about what never changes.
  • Owning your presence in an age that wants to rent it to you.
  • The craftsman in the age of the machine, an old question, made new.
  • Why the most human businesses will win the most automated decade.
  • Speed became free. Judgment became everything.
  • The quiet death of the homepage, and what replaces it.
  • Design is not how it looks. It is which decisions you were brave enough to make.
  • Why I still hand-code, in a year when I do not have to.

The Craft

  • Why one real photograph beats ten stock ones, and how to take the one.
  • The tyranny of the three-icon row, and what to put there instead.
  • White space is not empty. It is the most confident thing on the page.
  • A logo you can recognise from across a parking lot: the test that matters.
  • Why I set numbers in a different typeface than words.
  • The colour you use once is worth more than the five you use everywhere.
  • Tuning a guitar and tuning a layout are the same act of listening.
  • Fast is a feeling, not a metric, designing for the first half-second.
  • What a perfectly torqued bolt taught me about kerning.
  • The most expensive word on a homepage is the one that means nothing.
  • Measure twice, cut once, the carpentry rule that governs good design.
  • Silence between the notes: why what you leave out is the composition.
  • A button is a promise. Most sites break it.
  • The difference between finished and done.

From the Land & the Workshop

  • What pruning taught me about cutting features.
  • Rebuilding a carburetor and refactoring a codebase are the same patience.
  • My daughter asks why a hundred times a day. It made me a better designer.
  • The kitchen renovation behind the wall: why the hidden work is the real work.
  • Compost, the unglamorous system that makes everything else grow.
  • Diagnosing a engine noise is just debugging with your ears.
  • Why I finished the bathroom myself, and what it cost me to learn.
  • A song only works if you respect the silence. So does a brand.
  • Teaching a nearly-five-year-old to plant a seed: patience as infrastructure.
  • The right tool for the bolt: respect for the problem in front of you.
  • Frost on the late crop, and the redundancy I build into everything now.
  • Maintenance versus repair, the discipline that saves the season and the business.
  • What an old car restored by hand knows about owning, not renting.
  • Improvising on stage and shipping under deadline: trusting the practice.
  • The greenhouse runs all night so I do not have to. That is the whole idea.

The Honest Take

  • The thing I talk most clients out of.
  • Rent versus own: the difference between a platform and an asset.
  • Why I will not publish my prices, and what I do instead.
  • You do not need a rebrand. You need to decide what you already are.
  • The honest middle between doing it yourself and spending ten thousand dollars.
  • When I tell a client to come back in a year, and why they remember it.
  • What an everything-bundle really costs you.
  • The website that helps you is the one that knows what to leave out.
  • Why the cheapest site is usually the most expensive.
  • Trust is built the moment you say something against your own interest.
  • Maintenance is cheaper than repair, for cars, kitchens, and brands.
  • Who owns your customer data? Ask before you sign.
  • The quiet cost of being invisible, and how little it takes to fix it.
  • Why I would rather build you less.

Where It's Going

  • Faster is not always better, the heresy of the moment.
  • AI does not replace taste. It raises the price of having it.
  • The new literacy: knowing what to automate and what to protect.
  • The age of the one-person studio that ships like ten.
  • Why the next decade rewards the generalist who can actually build.
  • The agency model is unbundling. What replaces it.
  • Human-in-the-loop is not a feature. It is the whole design.
  • What gets cheaper, what gets precious, a map for the next five years.
  • Every small business will soon have systems only enterprises had.
  • The danger of automating the parts that were the relationship.
  • I let the machine move me faster only where I choose. Here is where I do not.
  • What I would tell a young designer starting today.
  • The greenhouse principle, applied to your whole business.
  • When the tool has one taste, your taste becomes the product.

The Reply

  • Someone asked: do I really need a blog? The honest answer.
  • A reader asked how I stay fast as one person. The real reason.
  • Do I need to be on every platform? No, here is how to choose.
  • How do you price work without a price list? Plainly.
  • What is the first thing you would fix on my site? A simple framework.
  • Is a one-person studio risky to hire? The fair version of the answer.
  • How much should a small business spend on a website? Honestly, it depends.
  • Should I use AI to write my website? Where it helps, where it hurts.
  • What do you say no to? More than you would think.
  • How do you measure if a site is working? Two numbers, not twenty.
  • Why do you start every message with Good Day? A small thing that matters.
  • Do you really build cars and kitchens too? Why it is the same skill.
  • What makes a client a good fit? Candidly.
  • How do you balance the studio, the land, and a young family? I am still learning.

The Quiet One

  • First light through the greenhouse glass. Six words.
  • The studio at dusk, one green light on. Only the date.
  • A single ripe strawberry, held. A line about patience.
  • The land under rain. Stillness as a strategy.
  • A hand-drawn curve beside its built version. Nothing else.
  • The signature, close up. A person stands behind this.
  • A guitar leaned against the desk at the end of a long day.
  • The kitchen mid-renovation. A word about the work behind the wall.
  • Small hands planting a seed. Growth, quietly compounding.
  • The last light through the workshop door. A word about warmth.
  • Rows in the garden, straight to the horizon. Order as care.
  • A closed laptop on a table outside. The hours, given back.
  • Tools laid out clean before the work. Respect for the problem.
  • Morning fog over the field. One sentence about beginnings.
05

How They Rank So High, and How You Get There

Good Day. Here is the honest mechanics of it. Choice OMG, Pixel Army, YEG Digital and the rest are not ranking because their work is better than yours. They rank because they have been quietly feeding three engines for years, and Google rewards consistency over time more than almost anything else. None of it is a secret, and none of it is out of reach for one person. It is mostly patience applied in the right order.

There are two different races happening on a Google results page, and you need both. The Map Pack, the little map with three businesses, is won mostly by your Google Business Profile and your reviews. The organic results below it are won by your pages, your content, and the trust other sites place in you. The agencies show up in both. So will you.

Why the agencies rank, the three engines

1 · The Google Business Profile engine (the Map Pack)

This is the single biggest lever in local search, and it is the one you can move fastest. Profile signals, proximity, the right categories, and the keyword in your business title, make up roughly a third of Map Pack ranking weight, and review signals (count, how recently, how steadily, and what they say) make up another sixteen percent or so.

A complete profile gets meaningfully more visits and is trusted more on sight. The agencies have had theirs filled out and collecting reviews for a decade. You have a profile and one five-star review. That gap is real, but it is the most closable gap on this list, it is filled in weeks and months, not years.

2 · The citation & directory engine

Search web design Edmonton and half of page one is not agencies at all, it is Clutch, DesignRush, UpCity and n49 directory pages that list those agencies. The agencies rank partly by living on the pages that already rank. A listing is a citation, and citation consistency is worth around seven percent of local ranking on its own.

The quiet trick: you do not have to outrank Clutch. You get listed on Clutch, and capture a slot on the page Clutch already owns. Same for DesignRush and the rest.

3 · The content & authority engine

The agencies run dedicated service pages for every term that matters, Edmonton Web Design, Edmonton SEO, Edmonton Branding, plus a steady blog. That gives Google many honest doors into the site and builds topical authority for the whole subject. Over years, other sites link to some of it, and that accumulated trust (domain authority) lifts everything.

This is the engine your new blog is built to feed. The content system in this folder is not separate from your SEO, it is your SEO, arriving one good post at a time.

Your ranked action plan, in the order that actually moves the needle
1

Own your Google Business Profile

Highest return, lowest effort. Start today.
  • Complete every field. Primary category Website designer; add secondary categories, Marketing agency, Graphic designer, Software company, that match what you do.
  • Set your service area to Edmonton and the surrounding region you actually serve, including just west of the city.
  • Add real photographs, the work, the workspace, you. Profiles with photos get more direction requests and more clicks.
  • Post weekly. A Google Business Profile post can be one of your daily lane posts, reused. It signals an active, real business.
  • Build reviews steadily, not in a burst. A consistent trickle beats a sudden pile. Ask happy clients, and when it is natural, let them mention what you did and where, Edmonton web design in a real sentence helps. Reply to every one in your voice, beginning with Good Day.
2

Publish the blog, on cadence

The compounding engine. Starts now, pays over months.
  • One post a day through the engine in this folder. Topical authority is built by consistency, not by any single brilliant piece.
  • Make sure every post is a real, crawlable page at jonathanellis.ca/blog with its own title tag and meta description, the blurb people read in Google, never left to chance.
  • Each post should mention Edmonton or Alberta naturally where it is true, and link once to a relevant service page. That internal link passes trust to the page you actually want ranking.
3

Sharpen the on-page foundations

One-time, do it once and do it right.
  • A genuine, distinct page for each money term: Edmonton Web Design, Edmonton Branding, Edmonton Automation, Edmonton SEO. Not thin doorway pages, real pages that answer the searcher.
  • Immaculate title tags and meta descriptions on every page. This is the cheapest SEO win there is and most sites leave it to chance.
  • Add LocalBusiness and Person structured data (schema) so Google understands who you are, where you are, and that a named person stands behind the work.
  • Confirm a sitemap is submitted in Google Search Console, and that the blog is fully crawlable.
4

Get listed where the agencies are listed

An afternoon of forms. Lasting return.
  • Claim profiles on Clutch, DesignRush, UpCity, n49, Yelp, and your Google profile, the same directories that already rank for your terms.
  • Keep your Name, Address, Phone identical everywhere, to the character. Copy it from one place and paste it everywhere. Inconsistency is the most common quiet drag on local ranking.
  • A free Clutch profile with two or three real client reviews can place you on a page-one directory listing for web design Edmonton without outranking anyone.
5

Earn a few real links

Slow, durable, high-value.
  • Your City of Edmonton work is genuine authority. Where it is public and appropriate, a credit or case study that links back is worth more than a hundred directory links.
  • Where a client's brand allows a discreet built by credit, take it. Each is a real link from a real local business.
  • A guest piece in a local business publication, or a partnership mention, compounds quietly over time.
6

Keep the machine fast and clean

Mostly already done, on your stack.
  • Your site is modern and likely already fast, that is a real advantage over the WordPress-on-a-template builds. Keep Core Web Vitals green.
  • Make sure Open Graph images and titles are set on every page so shared links look composed, yours already are on the main pages; extend it to each blog post.
  • Mobile first, always. Most local searches happen on a phone.
An honest word on timing

The Map Pack and review work can show movement in weeks. Competitive Edmonton organic terms, web design, the trades, the professional niches, generally take six to twelve months of steady work to reach the top few positions. The agencies have a decade of runway on you there.

The good news is the order above is deliberate. The fastest-moving, highest-return work sits at the top, so you feel progress early while the slow compounding work does its quiet thing underneath. Consistency is the whole game. The content engine in this folder is how you stay consistent without it ever becoming a chore.

06

Handoff & Next

The flagships are built from what is public, the City work, the greenhouse, the doctrine in your syllabus. The next batches get markedly better, and markedly more yours, when they are built from real stories only you can tell. Answer any of these in a voice note or a few lines whenever one sparks something. Each good answer becomes a post, often several.

Stories only you can tell · answer any that spark something
01
The City of Edmonton rebrand replaced an identity from 1977. What was the hardest part of touching something that old and that public, and what did you protect on purpose?
feeds · Field Notes, The Craft
02
On the 24,800-page rebuild, was there a single moment the scale truly hit you? Where were you, what were you looking at?
feeds · Field Notes
03
Tell me about Black Sky Diesel. What surprised you about designing for a heavy-duty diesel world, and what did those folks teach you?
feeds · From the Land, The Honest Take, Field Notes
04
Pacific Wine & Spirits, one of the largest importers in Canada. What did working at that scale change about how you think about a brand?
feeds · Field Notes, Where It's Going
05
DesignHouse Salon just passed ten years. What does it feel like to see something you branded still alive and working a decade later?
feeds · The Craft, From the Land
06
Viking Wood Splitter, branding the coolest way to chop wood on earth. What made that one fun, and what is the lesson hiding in the fun?
feeds · The Craft, The Reply
07
When did you first talk a client OUT of something, and how did it actually go? Did they remember it?
feeds · The Honest Take
08
What is the first automation you built that gave you real hours back? What did you do with the time?
feeds · From the Land, Where It's Going
09
What is the project that failed, or nearly did, and what did it permanently change about how you work?
feeds · Field Notes, The Honest Take
10
Why the greenhouse? When did the homestead and the work start to feel like the same thing to you?
feeds · From the Land
11
What is a piece of feedback from a client that you still think about?
feeds · The Reply, Field Notes
12
What do you say no to now that you would have said yes to ten years ago?
feeds · The Honest Take, Where It's Going
13
Commonwealth Games bid, Downtown Revitalization, what is it like to design something meant to shape a city for a decade?
feeds · Field Notes, Where It's Going
14
What is the smallest design detail you are unreasonably proud of in any project?
feeds · The Craft, The Quiet One
15
If a young designer in Edmonton asked you the one thing that matters, what would you actually say?
feeds · Where It's Going, The Reply
The pipeline, from this studio to your HQ agent
1 · Here (the studio). You and I think, write, and refine. Content is authored once in _source as JSON, and the build produces both the human studio page and the machine-readable files.
2 · The folder. Every post becomes content/<slug>/ with five platform files and a meta.json. The ledger logs it. This whole folder is what you hand to the HQ agent.
3 · Figma (when you bring me the MCP + a master design). From one master frame per format, I extrapolate every visual the posts call for, LinkedIn mockup cards, the 7-frame Instagram carousels, the mono numeral title cards, the Sunday photograph treatment, the TikTok title/end cards, all in your tokens, named to match each post's assetsNeeded.
4 · You film. For the video lanes you shoot the single take from the script, desk, greenhouse, garden, and drop the file in the post folder as video.mp4. The script, on-screen text, audio note and shot list are already there.
5 · HQ agent (your VS Code empire). It reads meta.json and the platform files, attaches the rendered visuals and your video, and posts to Instagram, Facebook, LinkedIn and TikTok on schedule, on its own.
6 · The loop. Before each new batch I read the ledger so nothing repeats, and we keep the queue about two months ahead.
Never post a caption that says like, subscribe, or follow for more. The HQ agent should treat those phrases as banned, the same as the voice doctrine treats deposit and cheap.
Every caption opens in your voice, Good Day where it fits, and stays grammatically immaculate. haha, never lol.
No invented numbers, ever. Only verifiable facts from your work.
A post is not eligible to schedule until assetsReady is true.
07

The Pipeline

This folder is the handoff. Content is written here, in Cowork, then moves through a small assembly line of agents until it is live on the blog and the social channels. The aim is to make it as automatic as possible, with a human gate at the front that stays closed until the output is reliably of Jonathan's quality, then opens on its own.

1
written
Cowork (Opus)
2
rewritten
Gemini 3.1 Pro
3
approved
You (human gate)
4
scheduled
System
5
live
Claude Sonnet (VS Code)
The gates · human now, automatic once earned
Gate Aauto
Release to rewrite
Your source content is already trusted. It moves to Gemini automatically once it lints clean.
Gate Bhuman
Approve the rewrite
This is the critical gate. Gemini is strong but can drift, especially on long form. You approve every rewrite until it has earned automatic.
Gate Chuman
Approve publish
Final eyes before anything goes live under your name. Opens to automatic after Gate B has.
A gate may switch from human to auto once its last 10 posts in a row cleared it with a clean voice_lint AND no human edit. If a later post ever needs a manual fix, that gate drops back to human for the next 10. Quality earns the automation; it is never assumed.
In the pipeline now · stage and voice-lint
2026-06-25
How I Talk You Out of Working With Mewrittenlint pass
2026-06-26
Why Everything Looks the Samewrittenlint pass
2026-06-27
The Greenhouse and the Machinewrittenlint pass
2026-06-28
Twenty-Four Thousand Pageswrittenlint pass
2005-07-24
My First Real Deadline Came at 250 km/hwrittenlint pass
2007-07-09
The Glass in My Pocketwrittenlint pass
2005-02-25
The Day I Walked Out of DevStudioswrittenlint pass
2005-09-19
The Things a Crowd Never Seeswrittenlint pass
2005-10-28
Ink, Lights, and Two in the Morningwrittenlint pass
2005-12-15
What School Could Not Teach Mewrittenlint pass
2006-02-21
Everything Got Glossywrittenlint pass
2006-04-18
The Year I Took the Web Seriouslywrittenlint pass
2006-06-27
Flash and the Cult of Motionwrittenlint pass
2006-09-12
Designing for the Wild, Democratized Webwrittenlint pass
2006-11-30
Print Is Not Dead, But It Is Quieterwrittenlint pass
2007-03-08
The Fold Is a Lie We Tell Clientswrittenlint pass
2007-09-25
Nine Fonts and a Workaroundwrittenlint pass
2007-11-14
A Client Asked for a Blogwrittenlint pass
2007-12-20
Two Years Inwrittenlint pass
2008-02-19
jQuery and the Joy of Less Codewrittenlint pass
2008-05-06
Designing Through a Downturnwrittenlint pass
2008-08-12
There's an App for Thatwrittenlint pass
2008-10-21
When Budgets Vanish, Restraint Winswrittenlint pass
2008-12-16
The Web Grew Up This Yearwrittenlint pass
2009-02-10
Twitter and the Art of 140 Characterswrittenlint pass
2009-04-14
An Ad Agency Inside a Hospitalwrittenlint pass