Book summary “Design Is a Job”: summary

Introduction

You spend years perfecting your craft, learning software, and studying typography, only to find yourself struggling when dealing with clients, money, and contracts. Art schools teach you how to make things look good, but they fail to prepare you for the harsh realities of the commercial world. You often accept low pay, endure endless revision cycles, and take the blame for projects that go wrong.

Mike Monteiro argues in Design Is a Job that design is not a mystical artistic calling.

It is a professional business discipline that requires mastering money, contracts, client communication, and ethics rather than just pushing pixels. You are not a service worker waiting for orders, but an expert hired to solve specific business problems. The book provides a practical roadmap to help you navigate your career, covering money, contracts, design processes, presentations, feedback, and agency leadership.

• How do you price your work correctly?
• What belongs in a legally binding contract?
• How do you present designs without losing control?
• When do you walk away from a bad client?

1. Defining the Designer

The popular myth of the magical creative reduces a designer to an accidental pixel-pusher and prevents real methodical problem-solving and honest criticism. Operating outside rules under the guise of pure inspiration makes teamwork difficult and forces other professionals to constantly undo misconceptions when clients ask to blue-sky projects without stifling creativity.

You must shatter the myth of the magical creative and embrace your true role as a methodical problem solver and gatekeeper who sells your own work directly.

A client once stood at the desk of Mike Monteiro with a PowerPoint comp marked up with unapproved changes decided in a meeting the designer did not attend. A designer's job encompasses a complete toolbox ranging from input and active problem-solving to output and direct selling. You must understand goals and gather information before opening any software.

• Ask why a design task is being done to establish goals.
• Gather information and research the landscape before designing.
• Impose order by turning ideas and requirements into artifacts and systems.
• Create novel forms that serve business goals rather than mere novelty.
• Talk to clients and stakeholders directly to sell work and get feedback.
• Act as a gatekeeper responsible for the work put into the world.

Referrals and Professional Reputation

Referrals are the lifeblood of a design business and the single most reliable way to secure high-quality clients without bidding wars. Prospective buyers trust colleagues who have previously hired designers, leveraging the transitive properties of trust. Designers should strive to be pleasant to work with rather than nice, because being nice often sacrifices honest communication for false harmony. Doing good work requires hard conversations, such as telling a client they are making the wrong call, which cannot happen if you are too afraid of breaking harmony.

A client called Monteiro stating that a referrer warned them the studio would not be shy about telling them they were wrong and would probably piss them off.

• Be pleasant to work with.
• Do good work.
• Get to know the client team and treat them well.
• Network by using a user-centered approach to learn what interests and motivates others.
• Write and publish opinions to remain visible.
• Maintain relationships by checking in without imposing chores.
• Treat referrals with respect to protect the referrer's reputation.

While referrals dominate, alternative business development methods like RFPs, outbound contact, and advertising have very low returns or require extreme targeting. Cold outreach acts like throwing seeds across concrete. Instead of spending 3 to 4 thousand dollars to co-sponsor a SXSW party, Mule Design spent 50 dollars on logo stickers that attendees shared online.

• Call the contact number on RFPs to find out who wrote it and build rapport.
• Use networking as research plus manners to find people in a position to hire.
• Blog about subjects and clients you want to work with.

Can You Do Good Work for This Client?

Evaluating potential clients through a systematic screener protects agency resources and ensures a proper fit. A prospective client's behavior during business development mirrors how they will act during the project, making red flags critical indicators to disengage. Mule Design utilizes a dedicated screener to evaluate goals, necessary capabilities, timeline, and budget before dedicating billable time.

• Check goals and necessary capabilities.
• Evaluate timeline and budget.
• Assess whether the project is core to the client's business.
• Disengage if red flags appear during initial conversations.

Designers must be as confident about money as they are about design and should never work for free or equity that cannot pay rent. Clients who ask for rates below market value or push for portfolio fodder inherently disrespect you, leading to poor project outcomes.

• Work for money that can be converted into rent.
• Submit a budget showing actual rates with discounts applied if working at a reduced rate.
• Refuse to work for free or solely for portfolio fodder.

Designers bear personal and ethical responsibility for the societal impact of the products and services they put into the world. Taking on clients whose business models cause harm makes you complicit in that harm, meaning creators must evaluate whether a client serves a real need. Mule Design passed on hiring a talented designer whose portfolio included work for a product that kills people, after the candidate stated he was just doing the design.

• Ask whether the problem the client wants solved is one you feel good attaching your name to.
• Verify if the client is serving a real need rather than exploiting a niche or causing harm.

2. Money and Contracts

There is always someone cheaper in the market. A high initial estimate gives room for negotiation, whereas an excessively low price cannot be recovered. If a client accepts a price immediately without hesitation, you likely charged too little.

You should charge as much as possible for your services and secure every project with a bulletproof contract drafted by a qualified lawyer.

Charging for Your Work

You can mention ballparks early to avoid sticker shock by giving a high-level estimate before writing a formal proposal. An $80–$120K project serves as a 700-level ballpark figure given to a client early before seeing project details. A written proposal is merely a prop for a sales presentation and should never be emailed on its own without a live defense. Getting a proposal ready means you are ready to sell it in front of the client's decision-makers. You must read the room, focus on selling benefits rather than features, and be prepared to justify your pricing with a detailed understanding of the work.

• Mention ballparks early to avoid sticker shock by giving a high-level estimate before writing a formal proposal.
• Never lower your price without taking something away, and never take something away without explaining the lost benefit.
• Never cut parts of your process, such as research, to lower the price.
• Present the proposal in person to the client's decision-makers instead of sending it via email.
• Go over as much or as little detail as the room requires.
• Focus on selling key benefits rather than features.

Working with Contracts

A contract establishes the ground rules, defines responsibilities, and protects both parties when unexpected disasters occur. Contracts are like prophylactic devices; they do not completely prevent bad situations, but they keep you free from additional liabilities down the road. They specify deliverables, deadlines, money exchange points, rights, and actions to take if the project collapses.

Monteiro's studio once worked with a client who brought in an unauthorized second designer to build a site. When the studio invoked the contract clause forbidding this, the client threatened to sue, but their lawyer Gabe intervened and made the threat go away. A lawyer's primary job is not to sue clients, but to ensure you never land in a position where you have to. Having legal backing gives designers the confidence to ask for what they are worth without negotiating their rights away.

• Separate the master contract from the statement of work.
• Include intellectual property transfers contingent upon full payment.
• Include a termination or kill fee to protect against canceled projects.
• Work with a lawyer on a solid master contract to cover frequent needs.
• Never talk to a client's lawyer directly without your own lawyer present.
• Reschedule meetings if unexpected client lawyers show up without your legal counsel available.

3. Process and Feedback

You must defend your proven design process against anxious clients while taking complete control of live presentations and structured feedback.

Sticking to Your Process

Clients often try to break the process due to anxiety about spending money or seeing rapid results. You must separate a client's valid goals from their flawed proposed plans, maintaining control over how the work gets executed.

Mike Monteiro turned down a high-profile, well-budgeted project because the client asked candidates to sketch initial concepts before doing any research. By standing firm on the requirement for research and process, the client responded by hiring them.

• Explain your process and how the pieces fit together at the start of every project.
• Refuse to draw or solve problems before fully understanding them through research.
• Stand your ground when clients attempt to rush, work out of order, or block access to people.

When clients panic, they default to habits in their comfort zones, which inhibits innovation. You must maintain clear communication, set proper expectations, and explain the concrete costs associated with waffling over decisions or altering timelines.

• Communicate project tracking continuously and address off-track moments quickly with a recovery plan.
• Inform clients of the exact cost in time or money whenever they delay a decision.
• Run meetings efficiently and do not train clients to think you have extra unmanaged time.

Presenting Design

A designer must present their own work because doing so is a core professional skill that builds rapport, shows confidence, and prevents the loss of crucial context through intermediaries. If someone else presents the work to the client, you cannot complain about feedback. Relying on intermediaries creates a game of telephone where questions and nuances get distorted into bad instructions. You should reveal work during a live call or meeting after setting the proper stage.

The author compares relying on intermediaries to the game of telephone played as kids, where chocolate becomes chick lit and let's go to church becomes let's go smoke in the alley. Presentations should be structured around project goals and business reasons rather than acting as a real estate tour of individual page elements. Walking a client through every element from the top left to the copyright notice invites arbitrary changes and personal subjectivity. Instead, you must lead with the reasons why features are present and how they meet the client's stated business goals.

• Stand up and walk to the head of the room.
• Announce who you are and what you do.
• Reiterate the goals of the project.
• Tell people how what you are about to show them will meet those goals.

Managing Feedback

Clients do not intuitively know how to provide useful feedback, so you must provide explicit guidelines that focus on business objectives and dictate what to ignore. Asking open-ended questions like do you like it invites subjective opinions and art critiques. You must provide written feedback guidelines before presentations that explicitly separate what to focus on, such as tone and structure, from what to ignore at that stage, such as missing elements or body copy.

• Focus on overall tone, voice, and structure.
• Ignore specific labels, body copy, missing elements, and things not shown.

Receiving feedback in the form of completed design comps from a client is extremely counter-productive and requires a firm response or account-level intervention. When clients deliver comps in Photoshop, PowerPoint, or Word, it forces you to reverse-engineer what problem they were trying to solve, wasting time and budget. This often happens because an internal client designer is unhappy with outside help, or because the client is trying to communicate visually.

At Mule, the author fired a client only once in ten years, and it was specifically because the client refused to stop sending design comps in violation of the contract. When raw feedback arrives, you must separate actionable points from non-actionable thoughts and organize them into clear categories before responding. You should read through feedback once calmly without mocking the client.

• Read the entire feedback straight through at least once.
• Separate actionable feedback from non-actionable feedback.
• Create a To-do list for immediate changes.
• Create a Disagreements list for bad ideas or things running counter to project goals.
• Create a Clarification needed list for items requiring a phone call.

4. Getting Paid and Working with Others

You need to enforce strict payment terms and collaborate effectively with developers, researchers, and peers while eliminating ego.

Startup promises that funding rounds are about to close mean the money is not currently there. You must ask directly what the client's budget is and whether it has been approved, treating financial conversations as a normal part of business development.

• Ask what the client's budget is.
• Ask if the budget has been approved.

Design is custom manufacturing, meaning a commencement fee is mandatory to mitigate risk since the work cannot simply be resold to someone else. Milestones must be tied to definite events like meetings rather than subjective metrics or site launches, and payment terms should be kept to net 15 rather than net 60.

• Collect a commencement fee upon signing the contract before kicking off work.
• Tie payment milestones to calendar events rather than metrics or site launches.

Working with Other Designers

You should welcome peer review because colleagues who share the same professional language can spot mistakes and explain how to fix them. Mike Monteiro stresses that while critiques can be harsh regarding the work itself, personal insults are strictly forbidden. The goal of a critique is never to make something just good enough or to praise hard work, but to get the design right.

In art school, students lined up personal artifacts for weekly critiques where they engaged in brutal takedowns to build critical thinking skills and thick skin, under the strict rule that personal comments about the author were banned on pain of expulsion from the room.

• Start by clearly defining the goals at hand.
• Discuss whether the goals were met and how well.
• Talk about the work, not the person doing the work.
• Recognize that everyone involved in critiquing has the best interests of the project and designer in mind.

When external agencies are brought in, they often find that internal designers have already attempted the job or produced competing comps due to insecurity or lack of internal support. You should collaborate instead of viewing each other as threats. External designers bring outsider status to navigate company politics, while internal designers offer vast product knowledge.

Monteiro once discovered a designer named Sam inside a client company who had already produced a full set of flows and wireframes. Instead of competing, they teamed up, and a huge percentage of the final product originated from Sam's pre-explored ideas.

• If you are on the services side, find the client's internal designers and leverage their internal knowledge.
• If you are an internal designer, reach out to incoming design teams and share insights.
• Swallow your pride and combine complementary skill sets.

You must maintain the confidence to know what you know, the humility to know what you don't, and the courage to respect differing viewpoints. Teams must establish clear roles to avoid duplicating efforts. Once you own a specific piece of a problem, teammates must trust you with it and never surprise you by hijacking your work or grabbing your mouse.

• Extend respect to other designers regardless of whether they are veterans or fresh faces.
• Establish clear roles and decide who owns what.
• Communicate often and give honest feedback.
• Never surprise another designer with your take on something they own.

Project managers keep projects on time, allocate resources, and serve as the voice of the client in the room. Creative tension occurs because you push for ideal work while project managers push for delivery on time and within budget. You must be realistic about time estimates, understand scope, and alert project managers immediately at the first sign of a missed deadline.

• Be clear about what each person is responsible for.
• Keep project managers informed of process as much as possible.
• Do not wait until a deadline is missed to alert the manager to a problem.
• Cut the creative routine by providing realistic time estimates and minding deadlines.

Good researchers conduct interviews with clients and customers and review analytics. They do not dictate design solutions, but they validate whether the team is heading down the right path by reporting user proclivities. You should sit in on as many user interviews as possible.

• Make it a habit to sit in on as many user interviews as possible.
• Check in frequently with researchers throughout the design process to validate decisions against data.

Information designers determine structure, taxonomies, and user flows, typically expressed through wireframes. Monteiro criticizes the common lie that wireframes do not imply layout, arguing that clients cannot be expected to ignore organized boxes. Visual and information designers should collaborate early using large whiteboards.

• Get the visual designer and information designer working together from the start on a basic grid, potential layout, and core functionality placement.
• Use large whiteboards to diagram solutions together and take pictures of the work in progress.

You should code or work at a fast pace directly alongside developers, riffing on each other's work to catch problems in real-time. Waiting to finalize static comps before involving engineers bakes mistakes into the project. Front-end and back-end engineers provide pragmatic decisions and technical constraints that improve design viability when consulted early.

Monteiro once initiated a signup flow redesign where team members argued step ordering based on legacy engineering constraints. By taking the idea directly to the lead engineer, they found a collaborative solution that improved conversion rates.

• Get into actual code or collaborative iteration with developers as early as possible.
• Explain the rationale for design decisions to engineers to leverage their pragmatic experience.

Content strategists organize and plan content because people visit sites for the stuff while design merely holds content in place. Design must be informed by content because containers cannot be built without knowing the size of what goes inside.

• Ask the two holy design questions: who is it for, and what are you putting in it?
• Work with content strategists early and often to align the container with the content size.

5. On Finding Yourself in Charge

Successful designers who step into management roles often fail initially because they try to act like heroes. You might grab a subordinate mouse to fix things yourself when patience wears thin. A design director job is no longer personal output. You must work with others so the team designs well together.

Directing other designers requires letting go of personal ego and the urge to micromanage, focusing instead on cultivating team growth and collaboration.

Leaders must provide enough leeway for designers to fail safely. You build trust through one-on-one reviews and tailor direction to each individual experience level. Intimate work-in-progress reviews work better than intimidating group presentations.

• Let go of ego and stop grabbing subordinates' mice to do the work for them.
• Give people enough leeway to fail so they can learn to recover.
• Conduct intimate, one-on-one work-in-progress reviews rather than intimidating group presentations.

Leadership and Management

People are social animals who feel secure when leadership provides clear expectations. When major mistakes happen with clients, you must own the responsibility rather than deflecting. When employees are failing, you must be completely transparent about performance problems.

Flat hierarchies are a myth because teams need clear leadership, and bosses must provide direct feedback, take responsibility for mistakes, and fire decisively when necessary.

Monteiro was once given a vague two-week warning to shape up at a job he hated, only to be fired anyway at the end of it. This experience taught him never to let an employee think they have a chance when they actually do not. False hope helps nobody on the team.

• Set clear goals and give regular updates on employee performance.
• When an employee is failing, give them specific steps to correct the problem and a timeline for achieving them.
• Be clear, quick, and humane when firing someone, ensuring termination never comes as a surprise.

10 Key Ideas

1. You must shatter the myth of the magical creative and embrace your true role as a methodical problem solver and gatekeeper who sells your own work directly.
2. You should charge as much as possible for your services and secure every project with a bulletproof contract drafted by a qualified lawyer.
3. Designers bear personal and ethical responsibility for the societal impact of the products and services they put into the world.
4. You must defend your proven design process against anxious clients while taking complete control of live presentations and structured feedback.
5. Clients do not intuitively know how to provide useful feedback, so you must provide explicit guidelines that focus on business objectives and dictate what to ignore.
6. Design is custom manufacturing, meaning a commencement fee is mandatory to mitigate risk since the work cannot simply be resold to someone else.
7. You should welcome peer review because colleagues who share the same professional language can spot mistakes and explain how to fix them.
8. Front-end and back-end engineers provide pragmatic decisions and technical constraints that improve design viability when consulted early.
9. Directing other designers requires letting go of personal ego and the urge to micromanage, focusing instead on cultivating team growth and collaboration.
10. Flat hierarchies are a myth because teams need clear leadership, and bosses must provide direct feedback, take responsibility for mistakes, and fire decisively when necessary.