What happens in the first 30 days of an embedded design engagement? Learn the week-by-week breakdown, common pitfalls, and how to prepare for success.
Most companies have never worked with embedded designers before. They know what it's like to hire an agency. They know what it's like to hire freelancers. But embedded design is different. It's a different working relationship. Different expectations. Different outcomes.
Companies starting an embedded engagement often have questions. What will the first 30 days look like? Will we see results right away? How much involvement do we need to have? Will the designer understand our business? How does this actually work in practice?
Understanding what the first 30 days looks like helps you prepare. It helps you get more value from the engagement. It helps you build the right working relationship from the start.
The first 30 days of an embedded engagement is critical. It sets the tone. It builds trust. It establishes how the designer will work with your team. Getting it right creates foundation for months or years of valuable partnership.
The first week of an embedded engagement is about getting oriented. The designer needs to understand your business, your product, your customers, your market, your challenges. You need to understand how the designer works, what they can do, how to work with them.
This week typically starts with an onboarding meeting. You brief the designer on the company. What problem are you solving? Who are your customers? What's your positioning? What are your goals? What are your challenges? The designer is taking it all in. Taking notes. Understanding context.
Real example: A SaaS company brings on an embedded designer on Monday. Monday afternoon, there's a two-hour onboarding meeting. The CEO and product lead walk through the company story. They explain the product. They explain the market. They explain why customers choose them. The designer is asking questions. Understanding the business.
During week one, the designer typically observes. They sit in meetings. They watch how the team works. They see how decisions are made. They see what the current challenges are. They're getting context before doing anything.
The designer might also do some preliminary discovery. Looking at the website. Looking at the product. Looking at competitor websites. Reading customer feedback. Getting a sense of the current state of things.
This week, there's typically limited output. The designer isn't producing finished work yet. They're learning. But there's a lot of value in this week. By Friday, the designer understands the business in a way they couldn't from a brief.
Real example: By Friday of week one, the designer can talk about the business intelligently. They understand the positioning. They know the key customer segments. They know the main challenges. They've built mental models of how things work.
By week two, the designer starts to form opinions. They start to see opportunities. They start to identify where design can have impact.
During week two, the designer typically has conversations with team members. Product managers about feature priorities. Sales team about customer objections. Support team about common problems. Marketing team about messaging challenges. They're gathering insights from different perspectives.
Real example: A designer talks to the support team. They learn that the number one customer question is "how do I export my data?" This is mentioned constantly. It's causing friction. The designer notes this. This is an opportunity. Maybe there's a design opportunity to make data export more prominent and easier.
During week two, the designer might present initial observations. What they're seeing. What they think are the biggest opportunities. Not finished recommendations yet. Just thinking out loud. Sharing observations. Getting team reaction.
This week is about building shared understanding. The designer and the team are building alignment on what matters. On where design can have impact.
Real example: In a week two sync, the designer says "I'm noticing that customers are confused about pricing. The pricing page exists but it's buried. And the product doesn't clearly communicate what tier you're on. I think there's a design opportunity here to make pricing clearer." The team nods. They've heard this feedback too. Alignment is forming.
By the end of week two, the designer and team typically agree on what the focus should be. What are the biggest opportunities? What should we tackle first?
By week three, the designer is ready to produce work. But it's not finished work. It's work-in-progress. It's collaborative.
During week three, the designer typically starts to sketch solutions. Design directions. Approaches to problems. They might create low-fidelity mockups. Wireframes. Rough concepts. The goal isn't finished design. It's to explore possibilities and get feedback.
Real example: The designer creates three different approaches to making pricing clearer. One approach adds a pricing indicator to the product UI. Another approach redesigns the pricing page to be more visual. The third approach creates a pricing comparison widget. The designer shares these three directions with the team. Not to present the final solution. To get feedback on direction.
This collaborative work is critical. The designer isn't designing in isolation. They're designing with the team. The team is giving input. The designer is iterating based on feedback.
Real example: The team looks at the three pricing approaches. They like elements of each. They say "the pricing indicator in the product is useful, but design approach one feels too cluttered. Could you try a cleaner approach? And the pricing comparison widget, we love that but can you make it more interactive? People want to play with it." The designer takes the feedback. Refines the concepts.
Week three is also when the designer starts to attend key meetings regularly. Standup meetings. Product meetings. Design reviews. The designer is becoming part of the team's rhythm. They're integrated into how decisions are made.
By the end of week three, there's momentum. The designer has done work. The team has given feedback. Things are moving forward.
By week four, the designer is refining initial work. Taking concepts and polishing them. Making them production-ready. Getting them ready for implementation or launch.
During week four, the designer typically works on taking the concepts that resonated and making them real. Higher fidelity designs. Refined visuals. Detailed specifications. Work that can actually be implemented.
Real example: The pricing indicator and pricing comparison widget concepts resonated. The designer spends week four refining these. Creating higher fidelity designs. Specifying how it should work in detail. Creating assets developers can use to build it.
Week four is also planning week. What happens in week five and beyond? What should the focus be? The designer and team discuss roadmap. They identify what should be next. What's the next problem to solve? What's the next opportunity?
During week four, there's also typically a reflection conversation. After 30 days, how's the engagement going? Is this working? What should we do differently? What's working well? This conversation helps calibrate the engagement.
Real example: In a week four sync, the team says "We love the work you're doing. We're seeing things we couldn't see before. One thing: we need faster turnaround on some of the work. Can you do some quicker design iterations instead of waiting for big refinement cycles?" The designer says "Absolutely. Let's do some rapid-fire design sessions. You give me feedback in real-time and I iterate on the spot." They adjust the working relationship.
After 30 days, what typically happens? What do you get from an embedded engagement?
First, you typically have initial design work. Concepts. Directions. Sometimes production-ready designs. Sometimes just exploration. But you have something to show for the work.
Real example: After 30 days, a company has three design initiatives in progress. A redesigned pricing page. A product UI change to make data export easier. A new onboarding flow. Not all are finished. But they're all in motion.
Second, you have a designer who understands your business. This is more valuable than it sounds. The designer can make smart decisions without asking questions all the time. They understand context. They understand constraints. They understand your positioning and strategy.
Third, you have a design culture shift. Teams start to think about design. Product decisions get run through a design lens. The designer influences discussions. Design thinking spreads through the team.
Real example: After 30 days, a company notices that in product meetings, people are asking design questions. "How would this look? How would users understand this? Is this on-brand?" Design is becoming part of decision-making.
Fourth, you typically have clarity on what's possible. The designer can articulate what design can accomplish. What are the highest-impact opportunities? What should we focus on? This clarity helps with prioritization and planning.
Fifth, you have a relationship with the designer. You know how to work with them. You've built trust. You've seen them deliver. You feel confident in them.
Real example: After 30 days, the team feels like the designer is part of the team. They're not a vendor. They're a team member. There's informal communication. There's trust. There's a real working relationship.
Understanding common pitfalls helps you avoid them.
First, not giving the designer enough context. If you don't invest time in onboarding, the designer won't understand your business deeply. They'll make generic recommendations. Invest time in week one. Make sure the designer really understands.
Second, expecting finished work too fast. Some companies expect polished designs by week two. This doesn't work. The designer needs time to learn. Give them room to explore. Finished work comes in weeks three and four.
Third, not involving the designer in meetings. If the designer is isolated, they won't understand how the team works. How decisions are made. Get them in meetings. Get them involved.
Fourth, not giving clear feedback. Designers need feedback to iterate. If feedback is vague or contradictory, progress stalls. Give clear feedback. Be specific about what's working and what isn't.
Real example: Designer shows initial concepts. Feedback is "These don't feel right." The designer is confused. That's not actionable feedback. Better feedback: "These feel too corporate. We want modern and playful. The first concept is closest but the color palette feels cold. Can you warm it up?" That's actionable.
Fifth, not letting the designer have autonomy. Some companies treat designers like executors. They want the designer to implement exactly what they ask for. This doesn't work. Designers need autonomy to push back. To suggest better directions. To think strategically.
If you're starting an embedded engagement, how do you prepare?
First, clear the calendar. Make time for the designer. Week one onboarding is important. Don't schedule the designer in the corners of your calendar. Make the first 30 days a priority.
Second, prepare context. Have your business story clear. Have your positioning clear. Have your customer insights clear. When the designer arrives, you can brief them efficiently.
Third, identify challenges. What are the top problems you want design to solve? Have a list ready. This helps the designer prioritize.
Fourth, align your team. Make sure your team understands the engagement. Make sure they understand that design decisions will be collaborative. Make sure they understand the designer's role.
Fifth, establish regular cadence. When will the designer attend meetings? When will you have design reviews? When will you do feedback cycles? Establish rhythm early.
Real example: A company starting an embedded engagement establishes this cadence: Monday morning designer standup with the product team. Wednesday afternoon design review with broader team. Friday wrap-up with leadership. This rhythm keeps things moving.
Sixth, set expectations. Be clear about what you expect from the designer. Be clear about timeline. Be clear about deliverables. This prevents misalignment later.
Several misconceptions come up frequently.
First misconception: The designer can start producing finished work immediately. Reality: The designer needs time to learn. They can't produce good work without understanding the business. Trust the process.
Second misconception: The designer needs to know exactly what to work on from day one. Reality: Part of the value is the designer identifying opportunities. Let them explore. Let them identify where design can have impact.
Third misconception: The designer will work independently and just show finished work. Reality: Embedded design is collaborative. The designer works with the team. There's feedback. There's iteration. There's a partnership.
Fourth misconception: The designer will do everything. Reality: The designer focuses on design. They can advise on strategy and product. But they're not the product manager. They're not the CEO. They have a specific role.
Fifth misconception: Results are immediate. Reality: Real change takes time. You'll see some quick wins. But the biggest value typically comes over weeks and months. This is a partnership, not a project.
At Rival, here's what typically happens in the first 30 days.
Week one, we do deep onboarding. We spend time understanding the business. Understanding the market. Understanding the customers. Understanding the challenges. We're asking lots of questions.
Week two, we identify opportunities. We share observations with the team. We build alignment on what matters. We identify where design can have the most impact.
Week three, we create initial work. Design concepts. Directions. Explorations. We're collaborative. We're getting feedback. We're iterating.
Week four, we refine and plan. We take concepts that resonated and make them real. We plan the next phase. We reflect on how the engagement is going.
By the end of 30 days, the company has clarity on design opportunities. They have initial work in progress. They have a designer who understands their business. They have momentum.
This is how embedded design works at Rival. We're not a project-based agency. We're not freelancers. We're partners. We embed into your team. We understand your business. We help you move the work forward.
If you're considering an embedded engagement, here's what to expect.
The first 30 days are foundation-building. You're building relationships. You're building understanding. You're building momentum. Don't expect polished deliverables immediately. Expect deep work. Expect collaboration. Expect the designer to understand your business.
After 30 days, you'll have clarity on opportunities. You'll have initial work in progress. You'll have a designer integrated into your team. You'll be ready to keep moving forward.
This is what we help companies do at Rival. We embed into your team. We understand your business. We collaborate with you to identify opportunities and move the work forward. We're not a vendor. We're a partner.
The first 30 days are critical. They set the tone for the entire engagement. Make them count.
"What is brand positioning? Learn how to define who you serve, what makes you different, and why customers should choose you over competitors."
Brand agency vs freelancer vs in-house designer? Compare costs ($2K-$300K), timeline, quality, and strategic value. Learn which model fits your needs.