Thoughts
Notes on running creative teams and making complex ideas clear.
Article 01
AI and the death of creative
I don't see AI as the end of creative work. I see a chance to give designers more time for the part of the job that drew many of us to it: noticing something, asking a better question, and finding an idea worth developing.
A finished design carries decisions that are easy to overlook. What does the audience need? What should they notice first? Is the idea appropriate for this person, in this situation? Producing an image or a page is one part of the work. Understanding why it should exist takes observation, conversation, and judgment.
AI can support that process. It can help a designer explore variations, organize material, or prepare a starting point to question and refine. Further along, it can assist with repetitive production and delivery. Less time spent adapting the same approved asset can mean more time spent testing the idea behind it.
That is the future I want creative leaders to build. We should teach people to use these tools thoughtfully, give them room to experiment, and keep them responsible for what they deliver. Checking accuracy, recognizing a weak idea, and understanding the audience remain part of the designer's job.
I can't promise that every role will stay the same. My argument is that replacing creative people misses much of the opportunity. If every saved hour becomes another production request, the team may move faster without doing better work. I would use some of that time for research, sketching, critique, and design thinking.
I learned to draw before I learned design software. A new tool can widen what I can try and shorten the distance between an idea and a finished piece. I still have to decide what is worth making. That is the creative work I want AI to support.
Article 02
Why creative organizations fail
When difficult projects keep going to the same few people, a team becomes dependent on their availability. They know the history, can fill gaps in a brief, and are trusted to get the work finished. That experience matters. It can also hide problems in how the work is organized.
At Vanguard, requests arrived through emails, direct conversations, and informal handoffs. Without shared intake, we couldn't see the full workload or set priorities across it. Establishing one intake point gave us a way to discuss capacity before assigning the next project.
We also needed to understand the team's skills. Availability alone couldn't tell us who was right for a particular assignment. A shared view of those skills made it easier to plan the work and identify where mentorship would help.
Those are practical responsibilities of creative leadership. A clear brief, a suitable assignment, and a decision made in time all affect what a designer can produce. I pay attention to where the same people keep having to rescue the process. That's often where the process needs work.
Article 03
What brand governance actually means
A brand guideline can specify a color precisely and still leave a team unsure how to make the next presentation. People need to know which decisions are fixed, where they have room to adapt, and whom to ask when the guidelines don't cover the situation.
That is the work of brand governance. Across markets and business units, people make small decisions every day about language, imagery, layout, and tone. A useful system gives them examples they can apply to the work in front of them.
I look for practical gaps: a template that no longer fits the content, competing versions of an asset, or an approval that depends on finding one person. Those gaps turn routine work into negotiation. Clear ownership, current assets, and a workable review process give teams more independence.
Consistency becomes easier when the right choice is easy to find. That leaves room for creative attention where a project actually needs it.
Article 04
Why AI changes operations more than creativity
Before adding AI to a creative workflow, I want to know where the team's time is going. Resizing approved artwork, preparing variations, sorting assets, and assembling a first draft each require a different kind of support. Treating them as one problem makes it difficult to tell whether a tool is helping.
I would start with a repetitive task that has a clear input and a result someone can check. Define what good looks like, decide who reviews it, and compare the full effort, including corrections. A faster first pass is useful only if it reduces the work that follows.
The handoffs matter too. Someone needs to know which version is approved, where it belongs, and what can be reused. AI won't resolve an unclear brief or an approval process with no owner. Those still need attention.
This is why I see such a practical role for AI in creative operations. Used carefully, it can give designers time back for exploration, conversations with users, and the decisions that shape the work. That is the benefit I would measure alongside delivery speed.
Article 05
Designing teams instead of org charts
An org chart shows reporting relationships. To understand how a team works, I also need to see who develops the first idea, who turns it into a system, and who brings the detail that makes it ready to use.
People contribute in different ways. One designer may be comfortable with an open brief; another may see how to simplify a complicated flow. Someone with deep production knowledge may spot a problem while it is still easy to fix. These strengths can disappear from view when assignments are based only on title or availability.
I start by mapping the capabilities the work requires against the skills we have. That gives us a better basis for assignments and a more specific conversation about growth. A gap might call for mentorship, a different partnership, or a hire. It doesn't always call for another layer of management.
People should also have room to develop beyond what they already do well. I want a team structure that supports learning while giving each project the experience it needs. The reporting lines are one part of that design.
Article 06
Business-to-human communication
A patient reading about a treatment and a plan sponsor reviewing retirement data arrive with different questions. Both need to find the information that matters to their decision. Neither should have to learn an organization's internal language to get there.
I work for that reader, even when the assignment begins with a business objective. Before choosing a headline or a layout, I want to understand what someone is trying to do, what they already know, and where they might hesitate. Those questions apply just as much to an internal process as to a public campaign.
Making information clear takes judgment. A shorter paragraph can still leave out the explanation a person needs. A complete page can still bury the answer. Language, sequence, and visual hierarchy have to work together, keeping the necessary detail within reach.
Business-to-human communication is how I approach that responsibility. I want someone to leave the experience better able to understand, decide, or act. That is the connection I look for between what an organization wants to achieve and what its audience needs.