From Builder to Architect: Your Complete PL-600 Power Platform Journey

In the fast‑evolving world of business technology, the ability to design and architect solutions using the Power Platform carries significant value. As organizations strive to digitally transform their processes, the need for professionals capable of bridging business goals with technical design grows. The PL‑600 certification serves as a strong indicator of a person’s ability to interpret requirements, translate them into technical solutions, and craft cohesive designs that involve multiple components of the Power Platform. This credential marks not just skill but depth of understanding and thought leadership in shaping business solutions that scale, maintain security, and fit within larger Microsoft environments.

At its core, the PL‑600 exam focuses on assessing your competence in guiding functional consultants, ensuring alignment between technical build and business requirements, and overseeing aspects such as data models, integration patterns, process automation, user experience, governance, and deployment strategy. Unlike technical certifications aimed at implementing specific features, PL‑600 situates you in the role of an architect—someone who envisions how tools like Power Apps, Power Automate, Power BI, and Dataverse work together in a structured, coherent system.

Professionals who aim for this certification are typically seasoned in Power Platform implementation, with experience collaborating with business stakeholders, understanding enterprise needs, and shaping custom solutions. Over time, such individuals accumulate deep knowledge of mapping user stories to technical patterns, crafting security and permission models, shaping data governance, and applying performance, reliability, and maintainability standards to solution design. The PL‑600 exam serves to validate that level of expertise.

The certification process starts with understanding the exam objectives. These span a set of domains, each mapping to architect-level activities:

1. Solution Vision and Design: You will demonstrate the ability to translate business scenarios into technical architectures. This includes understanding how system components interact, designing data flows, and defining governance models.

2. Data Model Optimization: You must design entities, relationships, and security models in Dataverse and ensure data is structured for performance and extensibility. Knowledge of normalization, choice of columns, and indexing strategies are key.

3. User Interface and Experience: You need to know when to apply canvas apps versus model-driven forms or portal experiences. The exam tests the ability to recommend UI approaches based on context, responsive design, and integration patterns.

4. Automation and Integration: This involves selecting between Power Automate, Azure Logic Apps, plugin extensions, and custom connectors. You must be able to define when each integration method is appropriate from security, long‑running process, tooling, and performance perspectives.

5. Solutions Lifecycle Management: You demonstrate proficiency in ALM (application lifecycle management), such as solution packaging, environment strategy, deployment pipelines, and governance guardrails.

6. Governance, Audit, and Monitoring: You must show understanding of platform governance, permission models, auditing strategies, data loss prevention, monitoring through metrics and logs, and security review sessions.

7. Change and Release Strategy: This domain covers how to plan for change, communicate with stakeholders, design rollback strategies, and align release schedules with business timelines.

Within each of these areas, the exam measures your ability to apply recognized patterns,  such as separation between core and customer-driven solutions, role-tailored security groups, event-driven architecture patterns, or multi-stage approval processes. The questions aim to assess how you reason through stakeholder needs, select appropriate platform tools, design stable and secure solutions, and outline execution strategies for real-world scenarios.

What differentiates PL‑600 from many other certifications is the breadth and integrative nature of its scope. It assumes you already have experience with building components. Instead, it tests whether you can assemble those components into a cohesive, scalable, sustainable architecture. You’re expected to think about things like deployment to multiple regions, data residency and residency models, environment-based permissions, API limits and licensing tiers, and cross-team readiness.

Going through the exam’s domains also encourages you to structure your mental model of how enterprise-grade Power Platform systems are built. For instance, in solution design, you learn to separate layers—platform versus application logic—or ensure proper layering between sprites—I mean UI—and APIs. You also form a habit of framing event-driven integrations—triggering actions based on record changes, custom connectors, or exposed endpoints. These design conversations—often rare in lower-level certifications—allow you to build patterns you can apply repeatedly in complex environments.

An often-overlooked dimension is user and change management. The certification recognizes that high-performing solutions are not built in isolation—they must fit within organizational processes. So, exam scenarios might involve managing stakeholder sign‑off steps, aligning release windows with finance cycles, or ensuring change records are maintained. These scenarios test your ability to embed solution design within existing governance structures and cultural norms.

Preparation for this exam usually begins with self-awareness. Many candidates come from backgrounds as functional consultants, Power Platform developers, or BI specialists. The certification nudges them into a broader consultative mindset. You start practicing by drafting solution diagrams, mapping functional requirements to technical components, and walking through versioning and lifecycle practices in your sandbox environments. But more importantly, you begin to practice explaining your decisions: “Why canvas app instead of model-driven? What performance bottleneck might we hit with a complex PCF? How does Dataverse licensing affect API use?” These are the types of thinking that the exam rewards.

Another distinguishing factor is its role in professional conversations. With PL‑600, you gain credibility to sit in architecture review sessions, propose Power Platform solutions in enterprise contexts, or lead governance frameworks for multiple teams. Beyond passing the exam, candidates improve their ability to facilitate workshops, validate design proposals, and think critically about alignment with corporate strategy, budget, and timeline.

Finally, the certification demonstrates a mindset shift from building first and documenting later to architecting holistically and implementing against a clear plan. That alignment shows through the exam questions, which frequently ask you to consider performance SLAs, extensibility, release management, and integrations with Azure, Dynamics, Teams, or Nx extensions. With that vision in mind, you prepare your processes, diagrams, validation steps, and stakeholder engagements before sitting the exam to earn a credential that signals true architect‑level understanding.

Strategic Study Methods and Hands-On Preparation for the PL-600 Exam

The path to becoming a certified Power Platform Solution Architect through the PL-600 exam is both challenging and rewarding. Unlike exams that test isolated technical skills, this certification assesses how well you integrate knowledge, solve problems architecturally, and apply platform capabilities to business requirements. Passing the PL-600 means proving that you think like an architect, considering scalability, governance, integration, data design, user experience, and application lifecycle management. The foundation of effective preparation is understanding that this is a scenario-based exam. The questions do not simply ask for definitions or straightforward configurations. Instead, they present realistic business needs, technical constraints, or governance considerations, and expect you to choose or recommend the best architectural approach. This means that preparation must include both conceptual learning and applied thinking. You must develop not only the ability to recall information but also the ability to reason through layered design decisions.

One of the most powerful preparation strategies is to build your own end-to-end Power Platform solutions in a controlled environment. This means taking a mock business problem and solving it through architectural design. Start by defining a use case, such as managing a company’s customer feedback system or automating an internal expense approval process. Map out the business requirements, break them into functional needs, and design a solution architecture. Consider what data entities you need, how to manage roles and security, which apps are required, what kind of flows will automate the process, and how to monitor and govern the application once deployed.

This hands-on practice gives you more than just technical fluency—it builds pattern recognition. When you encounter exam questions with complex requirements, your experience solving similar problems in your lab environment will guide your decision-making. For example, you’ll be able to identify when to use a model-driven app for structured navigation or when a canvas app better supports mobile workflows. You’ll understand that certain actions in flows might violate governance policies unless proper environment DLP configurations are in place.

Another strategic approach involves studying through design scenarios instead of siloed topics. Rather than reviewing Power Automate independently, study it in the context of a real use case. For instance, how would you automate customer onboarding across multiple systems? What happens if a step fails due to API throttling? How would you retry or roll back actions? Learning in this way creates neural links between components—between flows and Dataverse tables, between apps and security roles, between portals and Azure AD groups.

Developing architectural diagrams is also a crucial component of your preparation. Create solution blueprints that document entities, data relationships, flow triggers, app interfaces, and connectors. Use swimlanes to show user journeys, and document performance expectations at each layer. These diagrams train your mind to see the big picture. They also mirror real-world activities you’ll be expected to perform as a solution architect, and the ability to visualize architecture helps you approach exam questions with a structured thought process.

While studying, focus deeply on the environmental strategy and lifecycle management. Many exam questions test your ability to plan for development, test, and production environments. You must understand how to separate concerns, prevent data loss between environments, manage configurations using solution layers, and handle changes using pipelines. Practicing deployment using solution packages and manually observing how changes behave when layered across environments gives you real insight into the challenges of long-term maintenance.

Knowledge of licensing implications is another hidden strength. Many candidates overlook the impact of licensing on solution design. For example, using premium connectors or Dataverse capacities inappropriately can introduce unforeseen costs or break governance policies. In a solution architect role, you must weigh technical benefits against cost and feasibility. Understanding API call limits, plan entitlements, and licensing tiers allows you to recommend solutions that are sustainable and budget-aware.

It is also important to train yourself to think in trade-offs. The PL-600 exam does not test for perfect answers. It often presents options where each has pros and cons, and expects you to choose the most appropriate one given the scenario. You may need to decide between using Power Automate or a custom Azure Function for automation. You may be asked whether to store certain data in Dataverse or an external SQL system. These choices depend on factors like data volume, latency, compliance, and performance—all of which you must be comfortable evaluating.

As part of your preparation, simulate the role of a solution architect during the discovery and design phases. Practice conducting requirement-gathering sessions. Ask yourself how you would extract use cases from vague business goals. Build a library of open-ended questions you would ask stakeholders: What is the current process? What are your pain points? What systems are involved? How often does the process change? What are the compliance concerns? Practicing this kind of questioning builds your architectural intuition and prepares you for scenario-based exam prompts that require stakeholder alignment.

Also, pay close attention to governance. You must understand how to enforce DLP policies, segment environments for different business units, and monitor app usage across an organization. These are not minor topics—they represent the backbone of enterprise readiness. Study governance as both a policy framework and a technical implementation. Understand how to balance innovation with control. This mindset will not only help you pass the exam but also position you as a leader in responsible digital transformation.

To reinforce your understanding, make use of flashcard-style study notes focused on concepts rather than commands. For example, instead of memorizing how to build a flow, note the key design choices you must make—triggers, run frequency, error handling, and connector type. Write short notes about decision logic. Why would you use a business rule versus a plugin? When should you use embedded canvas apps inside model-driven forms? How do you ensure your app scales across roles and devices? These notes act as rapid revision tools and deepen your conceptual clarity.

To prepare for real exam conditions, practice answering sample questions under time constraints. Focus not just on getting the right answer but on how quickly you can understand the scenario. Read the last line of the question first—what is being asked? Then scan the scenario details and identify which facts are relevant. Train your brain to ignore extraneous detail and focus on core requirements. This skill becomes invaluable during the actual exam, where managing time is as important as managing content.

In the final stages of your preparation, run personal assessments. Rate your confidence across all the solution areas—data modeling, user experience, integration, lifecycle management, governance, and change strategy. Rank each area on a scale of 1 to 5 and prioritize the ones you feel least prepared for. Use these rankings to adjust your remaining study sessions, doubling down on weak areas while quickly reviewing your strengths to keep them sharp.

As the exam day approaches, simulate solution reviews. Pick a use case and pretend you are presenting your solution to a governance board or design authority. Explain your rationale, call out risks, defend your architecture, and articulate the value to the business. This practice not only helps you synthesize your knowledge but also strengthens your communication skills—an essential part of the architect role and a soft skill indirectly tested by scenario comprehension on the exam.

Keep your preparation fluid and adaptive. If you come across a concept that sparks interest, like telemetry integration or embedded analytics, dig deeper. Follow your curiosity. This creates an internal motivation loop and brings energy to your study sessions. The more curious you are, the more connections your brain builds, and the more resilient your knowledge becomes under exam pressure.

The strategic preparation for the PL-600 exam is about developing applied insight. Study through scenarios, build real solutions, draw diagrams, analyze trade-offs, simulate stakeholder conversations, and build a mental library of patterns. Remember, this is not a test of memorization—it is a test of vision. You are becoming a solution architect not just by passing an exam but by changing how you see problems, solutions, users, and systems. That change begins not on exam day, but every day you choose to think deeper, design smarter, and build for impact.

 Developing Architect-Level Thinking and Real-World Judgment for the PL-600 Exam

One of the most transformative aspects of preparing for the PL-600 exam is the evolution of your mindset. While many certifications measure what you know, this one measures how you think. Becoming a solution architect is not just about mastering the tools—it’s about developing judgment, perspective, and decision-making maturity that mirrors what happens in enterprise environments. To begin, let’s acknowledge that architecture is fundamentally about solving problems under constraint. Whether it’s time, budget, user resistance, technical limitations, or organizational policies, the architect’s job is to navigate these forces while delivering scalable, secure, and maintainable systems. That’s what the PL-600 exam is testing—your ability to weigh trade-offs and design sustainable solutions in less-than-perfect conditions.

One way to sharpen this thinking is to engage in scenario modeling. Imagine you’re working with a sales team that needs a new app to track customer interactions. The team is mobile, lacks formal process training, and already uses a mix of spreadsheets and email threads. From this single scenario, you can extract numerous architectural questions. Should the solution be a canvas app for flexibility or a model-driven app for structured navigation? Where will the data live? Do you use Dataverse, or is SharePoint adequate? What about offline access? Will security roles be based on geography, function, or a blend of both?

Working through these questions repeatedly in different business contexts helps build architectural fluency. You start to recognize recurring patterns: governance decisions affecting user adoption, data models driving performance bottlenecks, disconnected automation processes complicating support. The PL-600 exam leans into these patterns. It rewards candidates who don’t just understand individual features but who can connect those features into cohesive, strategic systems.

Another element to master is the principle of alignment. True architects don’t just build systems—they ensure that those systems reflect the needs of people, departments, and long-term business strategy. During preparation, challenge yourself to trace every technical decision back to a business goal. Why choose Dataverse? Because of better relationship modeling, security features, and integration readiness. Why introduce Power BI dashboards? Because executives need visibility into KPIs without manual reporting. Practicing this alignment makes you better prepared for questions that involve executive stakeholders or long-term scalability.

Equally important is the ability to design with governance in mind. Too many implementations fail because they were built without guardrails. As an aspiring architect, you must develop a deep understanding of how to control innovation without stifling it. Think about who can create apps, which connectors are allowed, how data is segmented, and how app performance and usage are monitored. The exam will often present scenarios where multiple departments share environments or where sensitive data must be protected under compliance policies. The right answers are the ones that balance autonomy with control, flexibility with risk mitigation.

To deepen your governance thinking, simulate how you would advise a large enterprise to implement a Power Platform center of excellence. What roles would you define? What automation would you apply to monitor new app creation? How would you categorize environments? Would you propose a training plan? These considerations force you to look beyond app building and think holistically about enterprise maturity. These are exactly the kinds of insights the PL-600 exam rewards.

Another major area of development is understanding the dynamics of cross-team collaboration. Architects rarely work alone. In real projects, they guide developers, collaborate with functional consultants, respond to security professionals, and present to executive sponsors. During preparation, visualize these interactions. What questions might a security analyst ask about your app’s data storage? How would a developer want you to define business logic boundaries? How do you defend a licensing choice in front of a finance director? Practicing these perspectives sharpens your ability to anticipate concerns and design more thoughtfully.

There’s also a powerful skill to build around layered decision-making. Architects often need to think in layers—data, logic, UI, automation, reporting, governance—and ensure these layers are cleanly separated but well-integrated. During your study sessions, evaluate your designs against these layers. Have you separated business rules from flows and plugins? Have you chosen the correct method for showing information to different users—dashboards, views, charts, or reports? Have you thought about how each layer might change independently without breaking the whole system? This layered view not only improves your designs but also equips you for complex exam scenarios.

Your communication habits also transform. Architects communicate differently. They speak in abstractions, use diagrams, outline roadmaps, and deconstruct problems into manageable components. While the PL-600 exam doesn’t test your verbal presentation skills, it does reflect this communication style in the way scenarios are framed. The questions are wordy, multi-faceted, and often simulate a project meeting, user story, or architectural review. Practicing how to digest and prioritize such inputs is essential.

Another critical trait is intellectual honesty. Architects do not know everything, but they know how to find out. When you encounter a technical limitation or unfamiliar scenario during preparation, resist the urge to ignore it. Instead, investigate. Learn why certain connectors have specific timeouts. Study why plugins outperform flows in high-frequency scenarios. Understand the performance impact of a 1:N versus N: N relationship. Each curiosity you pursue builds your problem-solving toolkit and makes you a stronger architect, both for the exam and in your role.

You should also grow comfortable with uncertainty. In the PL-600 exam, not every question will have a clear-cut best answer. Some will require prioritizing one requirement over another. For example, a scenario might demand both a low-code build and seamless integration with an external API that’s not easily supported. What do you recommend? Do you suggest a connector-based approach that needs additional licensing? Or a custom API bridge requiring a pro dev team? These are judgment calls. Practicing them improves your ability to defend your design choices, which is a key aspect of architectural leadership.

Developing architect-level insight also means understanding the lifecycle of a solution beyond go-live. How will the app be supported? Who owns the future roadmap? How are enhancements introduced safely? What telemetry will be collected, and what actions will be taken based on that data? Thinking through this end-to-end process demonstrates readiness to lead long-term solution success, not just implementation. The exam mirrors this holistic mindset, asking you to consider ALM, environment strategies, rollback plans, and deployment testing.

To bring it all together, build your mini portfolio of designs as you prepare. Choose three or four realistic scenarios and draft complete solution documents. Include diagrams, licensing estimates, security models, component selection rationale, and change management notes. This portfolio acts as your proof of concept, not for a recruiter, but for your growth. It becomes a practice field where you apply everything you’ve learned in a format that resembles real architecture work.

Preparing for PL-600 in this way transforms your brain into a design engine. It teaches you to slow down and analyze, to weigh options with clarity, to communicate complexity with simplicity. It prepares you to be the one in the room who connects business needs with technical tools, risks with mitigations, and systems with users. The exam becomes not a test, but a mirror—reflecting the maturity of your architectural thinking, becoming an architect is not a promotion—it’s a transformation in how you think, decide, and design. The PL-600 exam demands more than study—it demands insight. By modeling scenarios, simulating governance, layering your designs, collaborating mentally with stakeholders, and confronting ambiguity head-on, you build not only competence but confidence. You become the architect who doesn’t just build systems, but builds clarity, alignment, and value.

Post-Exam Growth and Lifelong Value of the PL-600 Certification Journey

Passing the PL-600 exam and becoming a certified Power Platform Solution Architect is an achievement that reaches far beyond a badge or digital credential. It represents a turning point in how you contribute to business transformation, how you are perceived within your organization, and how you shape your career trajectory. The first step after passing the exam is not to rush into the next certification but to reflect. You’ve just proven your ability to design complex systems, map real business needs to technical capabilities, and consider cross-cutting concerns like security, governance, and adoption. Now is the moment to digest what that means in your real work life. Ask yourself: How can I now apply these skills in my organization or client projects? Which areas of my architecture process can I now lead with more confidence? Which conversations am I now equipped to guide that I might have previously avoided?

Reflection turns accomplishment into application. Take an inventory of current projects or upcoming initiatives in your environment. Where is there confusion about data structure or automation design? Where could governance be improved? Where is app sprawl creating chaos? These are opportunities for you to step in and lead—quietly, confidently, and architecturally. You’ve trained to see these problems not as technical annoyances but as strategic entry points for improvement.

Another powerful step is to share your experience. Teaching is one of the most effective ways to reinforce learning and build visibility. Create a presentation, host an internal knowledge session, or start a weekly whiteboard series where you walk through real architecture patterns. Discuss topics like environment strategy, licensing impacts, or layered security in a way that others can learn from. As you teach, you’ll internalize your architectural thinking even further and begin to develop your voice as a leader.

You can also start mentoring others who are walking the same path. Every architect benefits from conversations with peers who ask, challenge, or refine ideas. Offer guidance to functional consultants aspiring to move into architectural roles. Review their solutions, challenge their assumptions, and help them frame trade-offs. This doesn’t just help others—it sharpens your intuition. Teaching someone how to balance low-code agility with governance, or when to separate solutions into multiple environments, forces you to articulate what you may instinctively understand.

Beyond your immediate environment, consider joining broader professional communities. Participate in architect roundtables, engage in low-code user groups, or contribute articles about your architectural journey. These spaces are rich with shared challenges and evolving patterns. By joining them, you stay current not just with new features, but with the shifting dynamics of enterprise solution design. The Power Platform is growing, and architects like you will increasingly be asked to guide how it’s adopted at scale across industries.

Now that you’ve passed the PL-600 exam, it’s also the right time to focus on the soft skills that support long-term success. As an architect, you are not only solving technical problems but also leading people through change. That requires listening with precision, communicating with clarity, and facilitating consensus between departments that may not speak the same language. Begin practicing those skills in your meetings and projects. Start noticing the political context of your architecture decisions—who will resist, who will champion, and how to navigate both with grace.

In many organizations, the role of architect is still emerging. The expectation may be vague or misaligned. Use your certification as a way to help define what that role should be. Set clear practices: solution review sessions, design documentation standards, reuse libraries, environment templates, and deployment gates. Propose lightweight but effective governance structures that guide innovation without blocking creativity. By doing this, you establish a cultural presence—the architect is not just the person with the plan, but the one who ensures consistency, clarity, and continuity.

One of the rarest skills you can now cultivate is the ability to influence without authority. Many architects do not manage people directly. Yet, they must lead cross-functional teams, secure stakeholder buy-in, and align competing priorities. Post-certification, begin practicing this skill with intention. Run design workshops, not as lectures but as facilitated conversations. Ask the right questions to draw out use cases. Use diagrams to guide discussions. Bridge technical limitations and business ambitions. Become the translator who helps both sides feel heard and who synthesizes the chaos into coherent direction.

Keep your architectural journal. Document lessons from each project. What went well? Where did your assumptions break down? What technical decision did you make that you would now reconsider? These notes will become your pattern library. Over time, they’ll reveal how your thinking has evolved, what blind spots you’ve overcome, and how your style of architecture has matured.

Post-certification is also the time to invest in sustainability. As an architect, you are now in a position to set things up not just to work, but to last. Design for supportability. Document with clarity. Create naming conventions that reduce confusion. Set guardrails that help future teams avoid mistakes. Build in telemetry that lets you monitor success and degradation over time. Encourage code reuse, solution modularity, and security practices that stand the test of team changes, business pivots, and technical upgrades.

You should also reflect on your long-term path. What kind of architect do you want to be? Some specialize in citizen development enablement. Others in enterprise integrations. Some in security and compliance. Some in automation and business process re-engineering. Begin identifying the themes that excite you the most and deepen your focus. Read books, join think tanks, or shadow senior architects in those spaces. The PL-600 exam may be your architectural starting line, but your future specialization is where mastery begins.

A key part of your evolution now involves pushing the boundaries of the Power Platform. Explore edge cases. Can a portal serve internal HR workflows with conditional access? How do you manage 50,000+ records in Dataverse with complex relationships and external sync? What happens when you stretch the ALM model across multinational divisions with conflicting deployment timelines? Find those edges—and experiment.

You’ll find that some of the richest growth happens in constraints. When something doesn’t work, when a feature breaks at scale, when a business user needs something the platform can’t offer directly—that’s when architecture truly begins. It’s no longer about the tool. It’s about the outcome. How will you get there, given the limits, the politics, the reality? That kind of thinking isn’t taught. It’s earned. And it begins the moment after you pass the exam and choose to keep building—not just systems, but insight.

In the long term, your certification will become a marker of your credibility. But your architectural presence—your habits, thoughtfulness, and the way you navigate complexity—that becomes your reputation. It will open doors you didn’t expect. You may be invited to steer enterprise initiatives, to sit on advisory boards, or to speak at global forums. When that happens, remember: you earned that seat not just by passing an exam, but by choosing to grow into the architect your ecosystem needed.

The PL-600 exam is not just a test. It’s a transformation. What you do after passing defines your value. Reflect. Apply. Share. Lead. Influence. And above all, keep building—not only on the platform, but within yourself. The mark of a true architect is not the ability to answer every question. It’s the courage to ask the right ones, at the right time, in the service of meaningful and lasting solutions.

Conclusion :

Achieving the PL-600 certification is far more than a professional milestone—it is a testament to your growth into a true architect. This journey, from learning platform capabilities to designing end-to-end enterprise solutions, transforms your technical skills into architectural insight. It sharpens your ability to connect business goals with technology, to navigate trade-offs, and to lead with clarity in environments where uncertainty and complexity are constant.

The PL-600 credential validates your ability to bring vision, governance, and integration together into cohesive, scalable solutions. It signals that you’re ready to lead—whether by designing secure environments, optimizing data models, or aligning technical paths with stakeholder needs.

But the true value of this certification begins after the exam. It lives in how you apply your skills daily, how you communicate design decisions, how you shape governance frameworks, and how you mentor others rising along the same path. The architect’s journey is not about tools—it’s about responsibility, influence, and strategic foresight.

As organizations deepen their digital investments, the role of architects will only grow more vital. By becoming certified, you’ve positioned yourself at the heart of that future. Let this achievement fuel your momentum. Continue learning, sharing, designing, and adapting. Lead not only with knowledge but with intent. The systems you architect will empower real people to do meaningful work—and in that, you’ll find the true reward of your PL-600 journey.

You haven’t just earned a certification. You’ve earned the trust to design what’s next.