Insights | Main Digital https://maindigital.com Understand today, optimize tomorrow Thu, 30 Apr 2026 15:54:42 +0000 en-US hourly 1 https://maindigital.com/wp-content/uploads/cropped-maindigital-favicon-32x32.png Insights | Main Digital https://maindigital.com 32 32 237410363 The liberal arts advantage in a high-tech world https://maindigital.com/the-liberal-arts-advantage-in-a-high-tech-world/ Thu, 30 Apr 2026 15:54:42 +0000 https://maindigital.com/?p=3989 Why skills like curiosity, empathy and judgment matter more as technology gets smarter

As we navigate an increasingly automated and AI-driven world, the value of a liberal arts education is more relevant than ever.

About 25 years ago, I earned my degree in economics. To me, this field has always been centered on understanding how people make decisions. Graduating during the dot-com boom, I entered the tech consulting field despite my liberal arts background. Initially, I didn’t understand why I would be valuable to technology projects, but over time, it became very clear.

Now, as the leader of a digital transformation consulting firm that helps organizations implement technology and artificial intelligence, I’ve realized that the skills I use most aren’t technical at all. They stem from my liberal arts foundation.

If I had to sum it up, there are three key lessons from studying the liberal arts that are more essential today than ever before.

Ask better questions

The first lesson is to learn to ask better questions.

Technology can generate answers instantly, but it doesn’t know what questions matter. I see this all the time in my work.

Recently, we worked with a client who had invested millions of dollars in a technology platform. From a technical standpoint, it worked exactly as designed. However, their sales and marketing teams weren’t using it.

The instinct was to focus on the system, adding more features, more training, and more enforcement. But when we stepped back and asked better questions, we uncovered something very different. There was no real incentive for anyone to use the system until the very end of the sales process, leaving leadership with no visibility into the pipeline, no ability to forecast, and no way to plan. So, deals would either show up unexpectedly…or not at all.

The issue wasn’t the technology; it was how the system aligned, or failed to align, with human behavior and incentives. Once we reframed the problem that way, the solution became much clearer. For me, that experience reinforced that the most important work isn’t always in the answer — it’s in asking the right questions from the start.

Main Digital CEO Sanam Boroumand speaks at a podium, with an audience listening.

Main Digital CEO Sanam Boroumand addresses a local college audience on the value of a liberal arts education.

Develop empathy and perspective

The second lesson is to develop empathy and perspective.

The ability to truly understand how other people experience a system — not how we think they should, but how they actually do. Most technology doesn’t fail because of code — it fails because it doesn’t fit how people work, what motivates them, or what they’re measured on.

What I’ve learned is that without empathy, we design systems for logic. With empathy, we design systems for reality. That shift, from thinking about the system to thinking about the experience, often determines whether something succeeds or fails.

And that ability to step into someone else’s perspective is something I use constantly. I also directly attribute it to my liberal arts education.

Exercise judgment, especially in ambiguity

The third lesson is to exercise judgment, especially in ambiguous situations.

AI is incredibly powerful, but it doesn’t carry accountability. It can generate recommendations, but it doesn’t understand context, trade-offs, or consequences the same way.

Therefore, the role of leaders today isn’t just to use technology; it’s to question it, interpret it and decide what to do with it. Increasingly, the risk isn’t that machines get it wrong; it’s that we stop questioning them.

Human skills matter more than ever

In an era defined by incredibly smart machines, it’s tempting to think that technical skills are all that matter. But my experience has shown me otherwise. The ability to ask better questions, develop empathy and perspective and exercise sound judgment has only grown more valuable as technology advances. These are precisely the strengths that a liberal arts education cultivates.

As we continue to embrace new technologies, it’s worth remembering that our most human qualities, those rooted in curiosity, understanding and thoughtful decision-making, are what truly set us apart. In the end, these skills will not only help us keep pace with change, but also lead it.

Contributed by Sanam Boroumand

]]>
3989
Packaged offerings: The new consulting standard https://maindigital.com/packaged-offerings-the-new-consulting-standard/ Tue, 24 Mar 2026 18:43:16 +0000 https://maindigital.com/?p=3986 A smarter way to achieve transformation without starting from scratch.

When businesses engage consultants, they often envision a tailored solution built from the ground up. While customization has its place, that doesn’t mean you have to start from scratch to achieve it.

There’s a growing case for packaged offerings. These solutions come pre-designed with proven frameworks, methodologies, and accelerators. They don’t cut corners. Rather, they leverage experience and foresight to maximize impact and minimize risk.

The efficiency advantage

Starting from zero means investing significant time in the planning stages before implementation can begin. Packaged offerings lift that burden. They leverage intellectual capital accumulated across multiple engagements to leapfrog the inevitable slow progress of early alignment, getting right to the phase where results can be delivered. Instead of reinventing the wheel, businesses benefit from solutions that have already been tested and refined.

Predictable outcomes

A familiar pattern in consulting is a client who knows they want to adopt a new technology, but doesn’t entirely know why. Without personal experience with the technology, their expectations can be vague and amorphous. A packaged offering has the benefit of built-in success criteria. A business can commit to a project with a much clearer expectation of what it stands to gain. Furthermore, it makes progress more trackable and manageable throughout the engagement. Following an already blazed trail makes the journey more predictable.

Reduced risk through proven practices

Every new implementation carries risk—technical, operational, and financial. Scope creep can inflate a project’s time and cost. Packaged offerings mitigate these risks by embedding best practices and guardrails from prior deployments. This means fewer surprises, smoother adoption, and greater confidence in outcomes.

Packaged, but not rigid

Given that every business is unique, why commit to a one-size-fits-all packaged offering? A common misconception is that packaged solutions are rigid, but in reality, they are designed to be modular and adaptable. They are dynamic roadmaps that include options, decision frameworks, and guidance, enabling them to work in a variety of environments.

Businesses can start with a core offering and expand as needs evolve, ensuring scalability without the complexity of building entirely new processes. Another way to look at it is that the roadmap actually gives you the ability to see where you are relative to the plan at all times, even when taking detours, whereas a completely bespoke engagement never knows exactly where it is or where it will end up.

Accelerated innovation

Perhaps the most overlooked benefit is that packaged offerings accelerate innovation. When foundational capabilities are delivered quickly, organizations can focus their energy on higher-value initiatives. It’s in these moments that they can differentiate themselves in the market. When the basics fall into place easily, there’s more time left over to solve unique strategic challenges.

A better model for business transformation

Packaged offerings represent a shift in how consulting value is delivered. They combine speed, reliability, and adaptability to help businesses achieve outcomes that would be far more costly and time-consuming to deliver through fully customized engagement models. For organizations looking to move fast and stay competitive, this approach can be truly transformative, while also remaining convenient and practical.

If your organization is ready to move faster without increasing risk, packaged offerings provide a practical path to meaningful transformation. By combining proven frameworks with thoughtful customization, you can unlock value sooner and focus your energy where it matters most.

At Main Digital, our experts partner with you to design and implement packaged offerings tailored to your business goals. If you are exploring new ways to accelerate results, contact us to learn how we can help.

Contributed by: Tom Weaver

]]>
3986
Designing with limitations https://maindigital.com/designing-with-limitations/ Fri, 13 Mar 2026 15:50:29 +0000 https://maindigital.com/?p=3979 Clear hierarchy, crafted content and strategic simplicity for constrained environments

What would design be without limitations? 

Designing in a challenging, classified environment with technological limitations poses significant challenges for the design team. The team must work within those constraints to create intuitive, clearly structured content and ultimately engaging experiences.  

We’ve embraced this challenge and turned it into an opportunity to create engaging work that transforms experiences. Despite obstacles, we’ve discovered these opportunities, which have sparked our interest and refocused us on key design principles, helping us elevate these experiences. 

Many articles have examined the effectiveness of design principles and methods of implementation. What I’m sharing here is our perspective on what has worked for us. We would love to hear about the strategies that have worked for you in similar situations and the reasons behind their success.  

Going back to the basics: Minimalist design aesthetic

A well-executed minimalist design aesthetic truly shines through its simplicity. When faced with limitations, the key elements we’ve highlighted serve as effective solutions: 

  1. Establishing a clear information hierarchy 
  2. Well-crafted content 
  3. Restrained use of typography 
  4. Strategic use of color 
  5. Embrace white space 

Establishing a clear information hierarchy

In design and communication, clarity isn’t optional; it’s key to understanding. A clear information hierarchy guides the viewer’s eye, so they instinctively know where to start, what’s most important, and how to navigate the content. 

Techniques such as spacing, scale, color, and contrast aren’t just aesthetic choices; they’re tools that direct attention and make information easy to understand. When the hierarchy is well-structured, users engage more deeply because they don’t have to work to find meaning; it’s built right into the flow.  

Well-crafted content

Great design relies on great content to give it meaning and direction. Clear, concise, and intentional writing transforms visuals into communication that connects with purpose — not by accident. 

When designers and writers align on a shared narrative, every element feels cohesive and purposeful. This consistency strengthens trust, reinforces messaging, and elevates the overall experience. 

The most effective content strikes the right balance—neither too much nor too little. A well-crafted narrative becomes the thread that unites design and message, connecting individual elements into a seamless, engaging story. 

Restrained use of typography

Using clean, readable fonts is essential for clarity and cohesion. Minimal designs typically rely on no more than two or three typefaces, each chosen to enhance readability and visual balance. Large, bold headers paired with simple body text create a strong, intuitive hierarchy that guides the viewer’s attention. 

Limiting the number of typefaces creates visual harmony and makes the design appear more intentional and professional. A restrained typographic system also reinforces brand consistency, ensuring that every piece of communication feels connected and recognizable. This approach enhances both usability and aesthetic appeal, allowing the content, not the styling, to take center stage. 

Strategic use of color and contrast

A restrained color palette fosters visual harmony and promotes brand consistency. Combining a client’s established brand colors with strategic accent hues helps keep the design balanced while highlighting key areas. This method prevents visual overload and creates a more unified, engaging experience. 

Color and contrast are powerful tools for guiding attention, helping viewers focus on key elements such as calls to action, links, and iconography. When used intentionally, they not only enhance usability but also evoke emotions and improve recognition. Thoughtful use of color and contrast converts design from merely looking good to communicating effectively with purpose and clarity. 

Embrace white space

Allow the experience to breathe. 

Whitespace is more than an empty background; it actively contributes to the design. It creates rhythm, defines structure, and helps users move through content naturally without feeling overwhelmed. Good use of white space draws attention to essential elements such as text, images, or buttons, making the overall design cleaner, more elegant, and easier to navigate. 

Using white space demonstrates confidence and clarity. It allows each element to stand out while maintaining the overall balance of the layout. Designs that use white space effectively appear intentional and thoughtful. 

So, next time you encounter a design limitation, revisit the basics and look for opportunities to enhance your designs — and contact our Main Digital experts for personalized solutions and support. 

Contributed by Bill Knight 

]]>
3979
Agentic AI: From theory to enterprise action https://maindigital.com/agentic-ai-from-theory-to-enterprise-action/ Fri, 27 Feb 2026 16:42:26 +0000 https://maindigital.com/?p=3972 Core components, real workflows and a 7-step deployment guide

Although less mainstream than its close cousin, generative AI, agentic AI is gaining attention across both the private and public sectors.  

Today, enterprise platforms are introducing intelligent agents that can plan tasks, make decisions, and take action without constant human prompting. While this sounds powerful, it can also feel abstract and hard to grasp. 

This article is a practical guide for business professionals who are curious about agentic AI, but unsure where to start. We will break down its core components, explain where it fits, and show how to start and scale with confidence. Along the way, you’ll find practical insights, tools, and examples to help you move from theory to action. 

Core components of agentic AI

Agentic AI and generative AI are often discussed together, but they serve quite different purposes. Generative AI creates – it is reactive, responding to prompts by producing text, images, or code. Agentic AI performs – once you set a goal, it can plan steps, call tools, and complete tasks without constant or regular input. 

Think of it this way: 

  • Generative AI drafts a client proposal when you provide the details and iterates as prompted. 
  • Agentic AI takes that proposal, submits it through your CRM, schedules a follow-up meeting, and updates your pipeline – all autonomously. 

Agentic AI combines reasoning, adaptability, and action. It uses large language models for decision-making, machine learning for adaptability, integrates with external tools, and maintains context across multi-step workflows. This autonomy makes it powerful in business environments where tasks are interconnected and time-sensitive.  

At its core, an agent has three building blocks: 

  • Model – Powers reasoning and decision-making. 
  • Tools – APIs or functions that enable the agent to read data and take action. 
  • Instructions – Guardrails that define behavior and safety.  

Where it fits

Agents shine where traditional automation struggles: processes with ambiguity, exceptions, or unstructured data. If your process relies on judgment or spans multiple systems, an agent can help. 

Examples by industry include: 

  • Finance: Agents compare transaction signatures across systems and automatically compile suspicious activity reports. 
  • Healthcare: Agents automate appointment scheduling, respond to patient queries, and escalate complex cases to humans. 
  • Manufacturing: Agents pull production metrics from SQL databases, analyze performance and update dashboards in real time. 
  • Enterprise Risk Management: Agents monitor logs and alerts to identify emerging risks and draft assessments. They also help prioritize issues and recommend actions to prevent problems from escalating. 

Traditional automation tools follow rigid steps. Agents can interpret intent, choose tools, and adjust their plan when something fails. 

In enterprise settings, the greatest value comes from end-to-end execution. Agents do more than draft a message. They retrieve, analyze, update, and process data.  

Step-by-step guide

Step 1. Choose one workflow

Select a workflow that wastes time on multi-step tasks or on unstructured data. Examples include triaging service tickets, preparing weekly portfolio updates, or compiling audit evidence from documents.  

Validate that success is measurable in hours saved or errors reduced.  

Step 2. Define the agent’s goal and instructions

Write a short, clear objective. Then convert your current operating procedure into numbered instructions that the agent can follow. Capture edge cases, such as missing data and timeouts. Keep actions explicit. For example, “ask for order number,” “call API to retrieve status,” and “if no result, escalate.”  

Step 3. Add only essential tools

Start with a small set of well-defined tools. Document each tool’s parameters, valid inputs, and expected outputs. Add validation layers at each tool call. Fewer tools with clear documentation will outperform many tools with loosely defined documentation.  

Step 4. Control the agent’s reasoning

Use structured prompting techniques and low-temperature (random and creative) settings to keep outputs predictable. Introduce checkpoints to decide when the agent should continue, retry, or stop.  

Step 5. Plan for errors and handoffs

Build management frameworks, error handling, and fallbacks. If the agent cannot complete a task after a set number of retries or reaches a high-risk action, transfer control to a human. This human-in-the-loop flow improves trust and performance early on.  

Step 6. Pilot in a private environment

If your data is sensitive, consider a private, on-premises deployment or a virtual private cloud to improve security, compliance, and auditability. Monitor logs and how fast it responds when under heavy use before scaling. 

Step 7. Measure ROI

Track time for the same tasks with and without the agent to measure return on investment (ROI). Multiply saved time by hourly costs. Add gains from higher output quality and faster turnaround. Decide when to expand to the next workflow. 

Practical insights along the way

  • Start simple: Taking on an overly complex workflow for the first agent slows adoption. 
  • Reduce creativity: Set a narrow temperature and clear exit conditions to keep the agent predictable and concise. 
  • Document everything: Log tool calls, retries, and decision points to support tuning. 
  • Iterate on prompts: Maintain one flexible base template rather than many one-offs. 
  • Plan for human-in-the-loop: Early intervention builds trust and catches edge cases. 
  • Security first. Align with SOC 2 standards and encrypt data in transit and at rest. 

 Pitfalls or mistakes to avoid

  • Too many tools:  Large toolkits increase failure points. Start small and enforce strict validation at each tool boundary. 
  • Weak instructions:  Vague steps cause confusion. Use existing procedures, make actions explicit, and document edge cases.  
  • Ignoring guardrails:  A lack of guardrails leads to unsafe or off-topic behavior. Use layered protections and human escalation rules.  
  • Skipping IT and security:  Deploying without information technology (IT) alignment creates long-term friction. Engage security and architecture teams early, especially for private deployments. 

Conclusion

Agentic AI, if implemented correctly, can be a powerful tool that extends the capabilities of its predecessors, such as robotic process automation (RPA), workflow automation, and chatbots.  

But don’t worry. You don’t have to start from scratch. At Main Digital, we help clients unlock agentic capabilities already built into leading platforms, including Pega, UiPath, and Salesforce. Our team knows how to configure, orchestrate, and optimize these tools to deliver measurable business value, without reinventing the wheel. 

If you’re ready to explore practical ways to leverage agentic features for automation, decision-making, and workflow orchestration, contact us today. We’ll help you design a focused pilot to accelerate adoption and deliver fast results.

Contributed by: Logan Johnson 

]]>
3972
Designing for trust: Ethical, sustainable and transparent UX https://maindigital.com/designing-for-trust-ethical-sustainable-and-transparent-ux/ Thu, 22 Jan 2026 16:49:17 +0000 https://maindigital.com/?p=3965 How to communicate data handling, permissions, and consent throughout the design lifecycle of digital products

“Trust isn’t a feature — it’s the emotional outcome of a well-designed, ethically grounded experience.” — Tara Bird

Trust has quietly become the most valuable design currency. Users no longer click “accept all” without hesitation. They’ve learned to question what data is being collected, why, and how it will be used.

We’ve all heard the horror stories: apps and services collecting far more personal data than they need to create “better user experiences,” tracking users without consent, and even selling personal information. With data breaches happening constantly, sometimes due to carelessness, trusting these companies has never felt more difficult.

Legal fine print and privacy policies no longer suffice. As interfaces grow more intelligent, more invisible — and more intrusive — the way we design consent, permissions, and data transparency directly affects how trustworthy our products feel.

Trust isn’t built with checkboxes and disclaimers. It’s built through small, visible acts of honesty.

So how do we intentionally build this into our products and experiences?

Go from user-centered to inclusive, cross-discipline design

We’ve long talked about user-centered design, but today’s challenges demand something deeper — collaborative user experience (UX).

In this approach, users aren’t data sources to extract insights from; they’re partners in shaping the experience. It’s an ongoing conversation that says:

  • “Here’s what we’re doing.”
  • “Here’s why it matters.”
  • “And here’s how you can change your mind.”

When users feel included in those decisions, they don’t just comply — they trust.

Design transparency into the experience

Transparency works best when it feels natural. Instead of making users dig through settings or policy documents, we can design clarity into the experience itself.

Speak to humans like a human

  • Replace abstract legal text with straightforward, empathetic language.
  • Instead of: “By continuing, you agree to the processing of personal data…” Try: “We use cookies to remember your preferences. You can change this anytime.”
  • A single line of clarity can do more for trust than an entire policy page.

Add layers of consent without overwhelming your users

  • Offer meaningful choices — not all-or-nothing ultimatums. Structure permissions in tiers: essential functions first, optional enhancements later, and full transparency always accessible. This approach transforms “agree or leave” moments into genuine collaboration.

Provide context and explain in the moment

  • Context is everything.
  • A prompt that says, “We’ll use your camera to scan receipts — images aren’t stored,” is infinitely more reassuring than a vague privacy notice buried elsewhere.
  • Design for understanding at the moment of interaction — not after the fact.

Build a visual language of trust

Visual design has an emotional impact that often speaks louder than text. Brand consistency, typography, spacing, and iconography can signal sincerity or conceal intent. A calm color palette, readable type, and familiar privacy symbols help users feel oriented and safe.

Design Element Why It Matters
Brand Consistency Creates stability, predictability, and clarity, showing users that the brand is reliable, honest, and dependable across every interaction
Icons Reinforce comprehension beyond words (e.g., locks, eyes, toggles)
Color  Blue and neutral tones suggest calm and reliability; aggressive reds often feel coercive
Whitespace Breathing room communicates openness and clarity
Typography  Clear, legible fonts convey honesty — avoid microtext or misleading formatting

In visual design, the smallest details can either strengthen or fracture trust.

Accessibility and sustainability as a form of ethics

Designing for trust doesn’t stop with privacy. It’s about intentionally prioritizing ethical design that is accessible and respects attention, energy, and the environment.

Accessibility

Every design choice, from color contrast to animation speed, shapes who can take part and how much effort it takes to do so. Accessibility isn’t just about checklists and requirements; it’s about making sure everyone can use and enjoy what you create, no matter their ability, device, or context. Features like adjustable text sizes, keyboard navigation, captions, and voice options are acts of respect and promote inclusion.

Sustainability

Every animation, image, and background process consumes resources. Choosing lighter assets, efficient interactions, and offering “low-data” modes signals respect — for both the user and the planet. Sustainable design isn’t just green — it’s considerate. It reduces noise, distraction, and digital waste, allowing what truly matters to stand out.

When we design with accessibility and sustainability in mind, we’re not just solving for usability — we’re building trust.

Real-world patterns that inspire trust

Looking for some interfaces and experiences that model these principles well?

  • Google and Fitbit have excellent privacy dashboards that provide clear summaries of what’s collected and why.
  • LinkedIn’s activity settings include granular controls that let you share only what’s necessary.
  • Use Slack or Google Meet? Notice the contextual prompts that ask permission for microphone access only when relevant.

In digital banking, you’ll receive data receipts that provide summaries of what was shared post-action.

Each of these experiences communicates the same message: you’re in control.

Summary

Designing for trust starts with humility — the understanding that transparency, ethics, and sustainability aren’t checkboxes but continuous commitments. The future of UX isn’t about hiding complexity behind sleek visuals; it’s about creating honest conversations between people and technology.

Every prompt, permission, and notification is a small moment of truth. When those moments are handled with clarity, and users feel informed and empowered to understand, decide, and even change their minds, trust stops being a goal — it becomes a natural outcome.

At Main Digital, we are passionate about designing ethical, sustainable, transparent, and collaborative user experiences. We’d love to help you build trust in your products. Reach out to our experts to learn more.

Contributed By: Sarita Loredo

]]>
3965
Understanding Design Tokens: The Building Blocks of Consistency https://maindigital.com/understanding-design-tokens-the-building-blocks-of-consistency/ Thu, 20 Nov 2025 05:52:01 +0000 https://maindigital.com/?p=3955 If you’ve ever wondered how apps and websites keep their look and feel consistent across teams, products, and even platforms — there’s a powerful tool at play behind the scenes: design tokens. 

Imagine you’re building a spaceship out of LEGOs. Each brick used in building that spaceship has a specific size, color and shape, and those attributes will be consistent no matter what you build. You can use the same gray 2×2 brick to make a house, a dinosaur, the Millennium Falcon or a replica of the Louvre. 

Just like the gray LEGO brick, design tokens are the foundational building blocks, based on your identity system or brand guidelines, of a design system, providing platform-agnostic variables across applications. These small but mighty reusable values include, but are not limited to:  

  • Colors 
  • Typography (fonts and sizes) 
  • Spacing (padding, margins, and grid) 
  • Sizing and border radius (how rounded a button is) 
  • Shadows, motion, and more 

Tokens are ideally stored in one central place (likely Figma), and they drive the appearance of everything — from the buttons on your website to the headings in your customer portal. The tokens directly correlate with our CSS classes, so it’s important to keep your Figma file up-to-date. 

Why design tokens matter

You don’t have to be a designer or developer to see the benefits of design tokens. Implementing this base layer of information into your design system has lasting impacts throughout a project lifecycle. The most influential benefits include: 

Consistency at scale

When used properly, design tokens ensure that all your digital properties share a common and recognizable look and feel. When elements are familiar to your users, there’s less tension throughout the digital experience. A button on your website will look the same as buttons on your app, portal and internal sites.  

Faster, smarter changes

The benefit of having your tokens in one place is that you only have to make a change one time. Want to update your brand’s primary color? Or increase font sizes for better readability? With design tokens, you update the value once, and it flows everywhere automatically. 

Seamless collaboration

Design tokens create a shared language between designers and developers, removing opportunities for miscommunication in handoff. This ensures that the design vision is accurately captured in the final product.  

Flexibility and support

Need to absorb a partner brand or develop support for visually impaired users? Design tokens make it easy to incorporate things like dark mode, accessibility improvements and optimization, or branded experiences for different clients, without redesigning everything from scratch. 

Types of design tokens

The list of tokens looks very similar in most design systems because only the core attributes of a system can be tokenized. These are the primary attributes that must stay consistent throughout all of your products and platforms. The following tables break down the most common tokens and what they typically define:

Token Type  What It Defines  Example 
Color  Primary, secondary, and tertiary palettes, text, backgrounds, borders, states (hover, disabled)  color-primary = #0070f3 
Typography  Fonts, sizes, weights, line spacing  font-size-large = 20px 
Spacing  Margins, padding, grid spacing  spacing-md = 24px 
Size  Widths, heights, icon and input sizes  icon-size-sm = 16px 
Border Radius  Corners for buttons, cards, etc.  radius-md = 8px 
Shadows  Levels of depth used for elevation or layering  shadow-sm = subtle shadow 
Motion/
Animation 
How things move or transition on screen  transition-fast = 150ms ease 
Opacity  Transparency levels (e.g., for overlays or inactive items)  opacity-muted = 0.5 

Best practices for using design tokens

1. Start with strategy

Define what tokens you’ll need (colors, typography, spacing, etc.) and decide how you’ll structure them. To build that structure, tokens can be divided into two categories: base tokens, which are typically neutral and not tied to any specific context and semantic tokens, which apply meaning to the base tokens by defining how they are used in specific elements in the design system. 

2. Use semantic naming, not literal

Clear and consistent naming conventions are key, but you can go a level deeper by sticking to names based on meaning rather than appearance. Avoid names like “blue-500” and instead use names like “color-primary” or “color-background-hover.” This will make it easier to change styles later without breaking design intent.

3. Document token usage clearly

Documentation is key to successfully integrating design tokens into your design system. In your documentation, include what each token is for, where to use it, and usage examples. This guidance helps everyone on the team (not just designers) apply tokens correctly. 

4. Review and evolve tokens over time

Tokens are not meant to be static elements; they will evolve over time with your brand and design needs. It’s best to treat tokens like code by versioning, reviewing, and depreciating unused ones. Regular audits ensure that design tokens remain relevant and accurate, helping to maintain consistency across your digital ecosystem. 

5. Integrate tokens into design and code workflows

One of the primary goals of using design tokens is to streamline the design-to-code process. It’s best to sync tokens between design tools and development environments to make the handoff as easy as possible. Store tokens in a platform-agnostic format (like JSON or YAML) and let tools or code transform them for web, iOS, Android, etc. Lastly, utilize tools that can automate updates, like Tokens Studio or Style Dictionary.  

Final thoughts

Design tokens might seem like a behind-the-scenes detail, but they have a massive impact on how smoothly your team works and how polished your product feels to users. 

They’re the glue that holds your design system together, and they empower teams to move faster, with more confidence and less rework. 

If you’re ready to take your design system to the next level, our Main Digital experts can help. We’ll work with your team to create scalable, token-driven systems that keep your product consistent, flexible, and future‑ready. Contact us to start building a smarter foundation. 

Contributed By: Lia Geeter

]]>
3955
Ecosystem Thinking: The Business Case for Holistic Experience Design https://maindigital.com/ecosystem-thinking-the-business-case-for-holistic-experience-design/ Thu, 16 Oct 2025 14:09:30 +0000 https://maindigital.com/?p=3950 Aligning customer journeys and organizational value through connected, omnichannel strategies. 

In an era where seamless, multi-device, and multi-product experiences shape customer expectations, businesses can no longer think in terms of isolated touchpoints.  

Instead, leading organizations are shifting toward experience ecosystems: integrated systems that connect interactions across digital and physical channels. This approach not only improves the customer journey but also boosts operational efficiency, enhances data intelligence, and strengthens brand loyalty on a large scale. 

In our work with a government client, where we modernize and transform digital product experiences, we ask critical questions based on the following themes to ensure we are developing and guiding these digital experiences effectively.  

Why It Matters for Users

A well-designed experience ecosystem doesn’t just look good; it feels right to the customer. By connecting the dots across devices, channels, and moments, ecosystems remove friction, personalize engagement, and foster trust. The result? A smoother, more innovative, and more inclusive experience that keeps users coming back — and ultimately drives deeper brand loyalty. 

  1. Consistent Experiences Across Channels: Users no longer experience jarring disconnects when transitioning between different product experiences. An ecosystem approach ensures continuity, reducing friction and cognitive load. 
  2. Personalized and Context-Aware Journeys: Holistic design allows systems to adapt based on user behavior, preferences, and device context, providing experiences that feel intuitive and tailored. 
  3. Improved Trust and Brand Perception: A cohesive ecosystem reflects maturity and reliability. When every touchpoint feels visually thoughtfully connected, users are more likely to trust the brand. 
  4. Minimized Redundancy and Repetition: Users don’t need to re-enter information, redo tasks, or relearn interfaces. Ecosystems share data efficiently and create a sense of progress. 
  5. Greater Accessibility and Inclusivity: Designing with an ecosystem mindset often encourages the application of universal design principles, which ensure that users with varying abilities and contexts can engage meaningfully. 

Why It Pays Off for the Business

Building an experience ecosystem isn’t just beneficial for customers; it’s a strategic move for the organization. By unifying systems, streamlining operations, and sharing insights across teams, businesses gain the agility to adapt quickly, grow effectively, and deliver consistently. It’s an investment that drives innovation, enhances competitive advantage, and promotes alignment throughout the enterprise. 

  1. Stronger Brand Cohesion and Differentiation: Unified experiences reinforce a distinct brand identity. It becomes easier to stand out and remain recognizable across channels and platforms. 
  2. Better Data Integration and Insights: A connected ecosystem enables organizations to track behaviors across touchpoints, yielding richer insights into user needs and drop-off points. 
  3. Operational Efficiency and Scalability: Reusable components, design systems, and shared platforms reduce duplication, accelerate development, and make scaling smoother. 
  4. More Agile, Future-Proof Strategy: With a foundation in an ecosystem, it’s easier to add new channels (such as voice, augmented reality (AR), or artificial intelligence (AI) interfaces) without starting from scratch, which keeps the organization adaptable. 
  5. Stronger Cross-Functional Collaboration: Designing for ecosystems requires shared ownership among product, marketing, service, and tech teams, fostering collaboration that breaks down silos. 

Designing experiences as ecosystems isn’t just a UX trend; it’s a business strategy. It minimizes friction for customers, increases engagement, and aligns cross-functional teams around a shared vision. For forward-looking organizations, shifting from touchpoints to ecosystems is essential to stay competitive, adaptable, and relevant in a swiftly changing market. 

Working with our government client, we take a holistic user experience approach, considering where a user is coming from, what information is most important for them to learn first, and how we can best serve their needs. 

How are your digital experiences benefiting your organization and, most importantly, your audience? If you’re ready to take them further, our Main Digital experts can help you design cohesive ecosystems that drive lasting impact for your business and the customers you serve. 

Contributed By: Bill Knight

]]>
3950
Why, How and When to Mature Your Intelligent Automation Program https://maindigital.com/why-how-and-when-to-mature-your-intelligent-automation-program/ Tue, 30 Sep 2025 17:33:07 +0000 https://maindigital.com/?p=3941 From pilot wins to enterprise impact, scale your intelligent automation program with purpose. 

A major appeal of intelligent automation (IA) is its ability to deliver quick results. Compared to other technology platforms that also promise increased workflow efficiency and productivity, IA tools like robotic process automation (RPA) and agentic AI can be implemented relatively quickly, with minimal personnel and infrastructure requirements.

While an intelligent automation program could always be planned and started at a large scale, the nature of the technology makes it ideal to start small. A business can get its feet wet with a pilot IA implementation and see results within a matter of a few weeks or months. Starting this way allows the team to learn while building, blazing a trail and producing assets that can accelerate future development. Regardless of business size, this is a practical, logical entry point.  

Then, after that first automation goes to production and everyone celebrates the achievement, the easy thing to do is grab the next candidate off the top of the pile and repeat the process with the same people. Doing this means you don’t have to transfer knowledge to new team members, expand the program’s information technology (IT) footprint, or add management overhead. This light and lean team could theoretically operate indefinitely, ticking off one process after another, delivering the benefits of the highly flexible IA technology. In fact, it might seem like a mistake to interrupt that chemistry by introducing new costs and complexity.  

However, at some point, this “if it’s not broken, don’t fix it” philosophy will hold them back from realizing their full potential. We will examine how scaling and maturing your IA program can compound your successes at a relatively low cost, and help you identify when it’s time to take these steps. 

Step 1: Formalize Pipeline Generation

One of the first signs that your IA program is being hindered by its small size is an inconsistent pipeline of project ideas. A small pilot team will likely consist of a small number of developers, analysts, and subject matter experts (SMEs). The role of the SME is to use their in-depth knowledge of business processes to provide ideas to analysts and developers, who turn them into automations. Initially, this relationship is efficient, as the SMEs will have multiple high-priority ideas. Over time, though, the ideas will come more slowly as the SME finds themselves reaching farther outside their field of knowledge to source projects.

One solution might be to move the development pod to new SMEs in new departments; however, each time you do that, you start the learning curve over again.

Instead, this is the ideal time to construct a system for managing the pipeline.  

  • Create a template for automation proposals 
  • Set up a mailbox for submissions 
  • Dedicate a small block of time weekly to evaluate submissions 

Your stalling pipeline is now accelerated, as your SMEs no longer need to put in the legwork of sourcing ideas; now the ideas come to them. Furthermore, individuals across the organization with ideas have a formalized pathway to participate in the program. The pipeline becomes a public document that anyone can interact with.  

Step 2: Initiate Federated Development

In addition to ideas starting to trickle in more slowly, another trouble point you may experience is long, sluggish discovery phases. You have an idea that you know is a good one, but the process of transferring all necessary knowledge from the SMEs to the development team becomes the longest phase of implementation.  

This is a great time to implement a federated development program. While the SME can be invaluable in teaching business processes to the development team, an even shorter path is for the expert to do their own development.  

Employees who know a process they want automated can be encouraged to build their own automations and add them to the program’s work pool.  

What they initially lack in expert automation skills will be overcome by their knowledge of the business and the processes they choose to automate. They are the people who know best which tasks consume the most time, and how to ease that burden.   

With these individuals at the controls, the discovery process becomes simple. Granted, it might seem impractical or even risky to open the doors to anyone without those basic automation skills to start building automations, but you wouldn’t do so without guidance and oversight.  

Step 3: Generate Training Playbook

The first step in guidance and oversight is training. One option for training citizen or federated developers is a classroom program where a teacher is selected or brought in to instruct a specific group of individuals. However, the appeal of intelligent automation tools in the first place is their ability to be deployed without major investments, including personnel.  

Rather than scheduling classroom time with dedicated trainers, employees interested in federated development can be enabled and empowered to train themselves. After a few development cycles with the pilot team, you should have accumulated a substantial collection of assets to assist in development.  

These can be compiled into a custom playbook:  

  • List of online training courses 
  • Sample practice projects 
  • Infrastructure enablement checklist  

By making this accessible to any potential federated developer, you democratize development, giving anyone with initiative the ability to train themselves to create their own automations. 

Step 4: Establish Enablement Repository

Once those federated employees are ready to begin developing in earnest, they will need a resource to provide guidance. Following the training playbook, additional assets can be created to guide them along the way.

A central repository can be hosted online, serving as a one-stop shop for everything they need to know: 

  • A technology selection worksheet to guide the developer through options for tools, ensuring they are using the right one for the job 
  • Documentation templates make it easy to document their build 
  • A best practices handbook lays out all the guidelines they need to follow to stay in compliance 
  • A test plan tracker allows them to thoroughly and comprehensively test their work 
  • Last, a build and deploy checklist can be a step-by-step guide through the entire process 

When complete, this repository becomes a tremendous tool and a home base for all federated development. As a final safeguard, once the developer has trained and guided themselves through the development process, they can submit their project to a review board for approval. You now have a main hub and roadmap for the entire federated IA program.  

Step 5: Build a Champions Network

Up to this point, every step described for maturing your intelligent program has prioritized minimizing staffing overhead. Through the power of self-actualization, a company can watch its employees trade repetitive job responsibilities for the highly engaging and rewarding practice of automation engineering. Eventually, though, most people can only make it so far independently. They will need support to get past roadblocks.  

With the tiered approach of a champions network, support can still be provided while continuing to prioritize self-sufficiency: 

  • Communications channel for peer-to-peer exchange of ideas 
  • Nascent developers can support one another by answering questions, sharing reusable code, and offering ideas and inspiration.
  • Recurring open-door sessions 
  •  More accomplished developers can deliver lectures, demo projects, or conduct live brainstorming sessions.
  • Contact list for support escalation 
  • When developers encounter problems that their peers can’t solve, this list shows them who to contact directly for help, without the runaround or hassle of opening a general ticket with their IT department.

A network like this, connecting developers of all skill levels, doesn’t just answer the FAQs of first-timers. It transforms your democratized group of individuals into a collaborative and innovative workforce far greater than the sum of its parts.  

Step 6: Codify Change Management

The last major bottleneck that crops up in immature intelligent automation programs is usually user awareness and acceptance. As the small, dedicated development team goes through the phases of discovery, development, testing, and release, they perform their due diligence by identifying every process and individual their automation will impact and communicating the impact to all relevant parties.

Without this communication, users who could benefit won’t buy in, conflicting processes will remain in place, and confusion about what is happening and why will lead to wasted time and resources. It’s reasonable to expect the team to handle change management on the first few automations they build, but as they accumulate a library of automations, even their most carefully laid plans will have blind spots.  

The solution to this is a structured change management system.  

Introduce a standardized template for announcing the launch of new automations that clearly indicates:  

  • Function 
  • Schedule  
  • Impacted systems and parties 
  • Support contact information is the first step 

Next, the same repository created for the federated model can also host an information sheet detailing each automation in production, with links to comprehensive documentation. Now everyone in the company understands what to expect from the automation program and where to find more information.  

Finding the Right Balance

We just walked through the steps of maturing an intelligent automation program. What began as a small, dedicated team picking off the lowest-hanging fruit has evolved into an enterprise-wide perpetual-motion machine, transforming the company’s efficiency. It is important to emphasize that these are not competing visions.  

There is a temptation to view this growth as a departure from the principles that originally made IA effective. By introducing new people, processes, and regulations, it appears that there is a risk of compromising the rapid gains delivered by a lean program. As we saw, however, this method eventually hits bottlenecks and slows down, failing to maintain the initial rate of delivery. Facilitating growth becomes the only way to keep moving forward.  

Likewise, attempting to operate at this scale before you are ready will lead to inefficiencies and create overhead that might prevent the program from ever reaching its potential. The IA tools we implement are well understood, and this foundation of knowledge allows us to effectively deploy from one organization to the next, incorporating all the lessons learned along the way. Yet, each organization is different. Starting small allows us to deliver great results for your organization while establishing relationships, defining processes, and generating custom assets that will facilitate an effective maturing process.  

Main Digital Can Help

Main Digital’s IA process is designed to work with your business, identifying inefficiencies in both your business processes and your technology programs themselves. The result is a collaborative engagement that grows and evolves with you, ensuring your intelligent automation program delivers maximum results from the outset and continues to yield benefits into the indefinite future. Contact us to learn more.

Contributed By: Tom Weaver

]]>
3941
Pilot Programs: Lessons Learned https://maindigital.com/pilot-programs-lessons-learned/ Fri, 12 Sep 2025 18:50:49 +0000 https://maindigital.com/?p=3934 Actionable insights for launching pilot initiatives that boost team buy-in, measure impact and drive transformation.

In 2024, I led a design thinking pilot program for a global food and beverage company. I worked alongside developers, business stakeholders and management for three months, teaching the group new methods and tools to increase delivery velocity, brand fidelity, user experience excellence and quality of requirements.

While the details of the engagement will be the subject of another post, I wanted to share some of the lessons learned about how to conduct a pilot program effectively. While this pilot focused on introducing a design thinking mindset and design system to the company’s Power BI environment, these insights can be applied to a wide range of pilot programs.

Lesson 1: Maximize Team Buy-in as Early as Possible

Teams are busy. They don’t always want to commit the time and brain power to learn new tools or processes. Change resistance is present in any environment. Breaking down that resistance as early as possible is critical for a successful pilot.

First, lay out precisely what the pilot will be covering. By setting expectations for time commitments and responsibilities, and providing overviews of the new processes and tools covered in the pilot, you’re providing participants with a runway to organize their day-to-day and digest what is coming. Surprise is the enemy of smooth, and that applies doubly for a pilot.

Second, ensure that your pilot subject matter experts (SMEs) are available to answer any and all questions at any time. Though I was off-site for the majority of the pilot, we set up a Teams chat where questions could be asked and information shared. Frustration can lead to disengagement, so make sure participants feel supported at all times.

Third, make it fun. I don’t necessarily mean ha-ha fun, but there is no reason you can’t inject humor and creativity into any undertaking. Pilots can involve high-pressure situations, but like any great teaching experience, keep the mood light. Mistakes will be made, and that’s OK. That’s a part of learning. We all have to start somewhere.

Lesson 2: Start Small and Build Up

There are a few dimensions to this don’t-bite-off-more-than-you-can-chew lesson.

First, as opposed to starting a pilot with the entire team, consider starting out with a smaller (but functionally complete) pod. This allows you to spend more, higher-quality time with the participants as opposed to being spread too thin. These initial participants, once they’ve gotten a few cycles under their belt, can then become teachers helping to instruct others on the team. Teaching others is also a great way to learn, as it helps to solidify concepts through repetition.

Second, pick a project of modest scope. Your pilot shouldn’t try to boil the ocean, but should rather focus on a small, achievable goal. Perhaps this is the first stage of a larger project, or a new concept in the backlog that you haven’t yet been able to work on. It’s important to understand that velocity will be impacted as participants focus on learning new processes and tools. Keeping the project small will help them maintain focus and engagement, as well as minimize anxiety.

After the pilot has been running for a few weeks and your initial participants understand the basic concepts, you can introduce more members to the pilot team. At this point, hopefully your initial group is enthusiastic about the pilot—they’ve seen the light!—and their enthusiasm will help sell the new way of doing things.

Lesson 3: Document Everything: The Good, the Bad, the Ugly

Initially, new ways of tackling work may seem overly abstract. How can these things be applied to OUR environment? What are their impacts? What works best? What doesn’t work?

A good way to make the abstract tangible and approachable is through documentation. Keep all your artifacts from the pilot, no matter how insignificant: they provide an important record that the team can refer back to later. And as you bring in other team members, you now have examples of the new processes that will be meaningful to them.

You may also ask your participants to keep a brief journal of their experiences. At the end of each day, give them 10 minutes to document what they experienced that day: what was difficult, what questions they have, what they wished they had done differently, etc. These notes are important for fine-tuning the pilot as it evolves and will help reinforce what participants learned that day. Review these notes at the beginning of the next day and talk through any issues or questions.

Lesson 4: Understand Where You’re Coming From and Where You’re Going

And last, but not least: measurement.

The whole point of a pilot is to improve something. That something could be team velocity, software quality, user satisfaction, brand adherence, accessibility, agility, etc. But you won’t know if your pilot has been successful if you don’t provide a baseline for performance. You can think of these as metrics, or key performance indicators (KPIs). Before you can connect the dots, you need a first dot.

An example: At the company, it was taking “X” weeks (we promised not to tell!) on average to develop a new Power BI dashboard. During the pilot, we were able to re-architect and redesign one of the most complicated dashboards in the Power BI environment in half the usual time. And this was a ground-up redesign where we questioned all assumptions about the environment and dash! Amazing, especially considering the team was learning new processes and tools simultaneously.

This example is powerful, but also a bit obvious. You’ll probably want your metrics to be more granular and touch across multiple dimensions.

If the thought of running a pilot program seems a bit overwhelming, don’t worry. Main Digital is here to help. If you’ve considered optimizing your team through the adoption of a new process or tool, reach out. We’re experts at it! Remember, Main Digital has the process aptitude of a Big Four consultancy, the data and technology competence of an integrator and the creativity of a design agency.

Contributed By: John Clarkson

]]>
3934
Untangling Complexity: Common Challenges in Developing Digital PPM Solutions https://maindigital.com/untangling-complexity-common-challenges-in-developing-digital-ppm-solutions/ Fri, 25 Jul 2025 16:37:16 +0000 https://maindigital.com/?p=3921 Lessons Learned and Actionable Tips for Digital Project Portfolio Management Success

Digital project portfolio management (PPM) solutions promise clarity, control, and alignment across projects and teams. But reaching that promised land is rarely straightforward.

Having worked on digital PPM implementations across multiple organizations, I’ve seen firsthand how even the best intentions can get tangled in complexity. The good news? Most of the challenges are common—and solvable.

In this article, I will share some of the most frequent hurdles I’ve encountered, along with practical ways to overcome them so that your next digital journey can be a little smoother.

Build or Buy? The First Big Decision

What Happens: Teams often get stuck deciding whether to purchase a ready-made PPM tool or build one in-house. Each path has pros and cons, but indecision or misalignment can stall progress.

Real-World Insight: The appeal to build in-house is understandable, but it’s often more wishful thinking than practical strategy. Unless your organization specializes in software development, maintaining an in-house solution can quickly become more burdensome than expected.

Recommendation: Consider low-code PPM platforms that offer a balance between customization and ease of implementation. These solutions often provide flexible pricing models based on usage, making them more accessible and scalable. Whether you build or buy, your team will still face the same technical challenges. By purchasing, you gain a faster time-to-value, access to industry best practices, ongoing vendor support, and the ability to refocus your internal resources where they matter most.

Work With IT to Maximize Support

What Happens: Moving quickly on a new solution without first aligning with information technology (IT) can create long-term friction. Reasonings typically include a desire to avoid delays, or the solution is deemed department-specific without plans to impact the broader organization.

Real-World Insight: In one case, a client initially developed a custom solution outside of IT. It worked—until it didn’t. When support was needed, IT hesitated to step in because the technology conflicted with other IT-supported solutions. What started as a quick win became a long-term liability.

Recommendation: Engage IT from the beginning. Even if the solution feels business-led, IT’s input is critical for sustainability, security, and scalability. A structured RFP process based on actual needs helps ensure alignment, gain buy-in, and build a foundation for long-term support.

 Start Simple to Avoid Overengineering the Solution

What Happens: Trying to solve every problem at once leads to bloated, complex systems that are hard to maintain and even harder to use.

Real-World Insight: Our team was contracted to support a solution that had become a monolith—too complex to scale and too costly to evolve. Every new feature added more weight.

Recommendation: Start simple. Define a core set of features based on real user needs. Use a phased release approach and build iteratively. Simplicity is your best friend, and fringe scenarios can be managed outside of the application.

User Involvement Is Key to Lasting Adoption

What Happens: When users aren’t part of the journey, adoption suffers. A great tool that no one uses isn’t a great tool.

Real-World Insight: A solution was developed without involving all end users in the requirements gathering or design process. The result? Confusion, frustration, and resistance.

Recommendation: Bring users in early. Create a champions network and use feedback loops to ensure actionable communication. When people feel heard, they’re more likely to engage.

Integrate Change Management Early or Risk Big Problems

What Happens: Even the best-designed solutions can fail without proper change management. People need time, training, and communication to adapt.

Real-World Insight: One rollout our team led failed, not because of the tool itself, but because not all departments were aligned on the solution—or even agreed on how it should be used.

Recommendation: Integrate change management into every phase of the project. Ensure processes are adopted first. Communicate often and train thoroughly. Make change feel like progress, not disruption.

Governance Matters: Align Teams Before They Drift Apart

What Happens: Without clear roles and responsibilities, development becomes chaotic. Citizen developers, core teams, and stakeholders can unintentionally work against each other.

Real-World Insight: In one case, lack of governance in a federated development model led to broken code, finger-pointing, and stalled progress.

Recommendation: Establish a steering committee. Define clear accountability. Utilize structured development practices, such as backlogs and sprints, to maintain alignment and foster visibility.

Manage Scope Creep Without Sacrificing Agility

What Happens: As excitement builds, so do the requests. Without boundaries, scope creep can derail timelines and budgets.

Real-World Insight: In my experience, I have seen the polar extremes with teams attempting to lock down every requirement upfront, while others have accepted change at any point. The first typically delays development and creates friction, while the other causes the development team to spin and fail to produce any significant value.

Recommendation: Lock down sprint backlogs but allow flexibility in the product backlog. Prioritize continuously and remain open to change, but don’t disrupt work-in-progress. Foster a continuous improvement mindset.

Break Down Departmental Silos to Build Unified Solutions

What Happens: Different departments want different things. Trying to please everyone can lead to a fragmented, inconsistent solution.

Real-World Insight: A department-led approach yielded a patchwork of personalized requirements that were difficult to integrate.

Recommendation: Align on a shared vision. Standardize where possible. Use a core hub architecture to ensure a single source of truth, while allowing some flexibility at the edges.

Future-Proof Your Solutions With Scalable, Modular Design

What Happens: A solution that works today might not work tomorrow if it’s not built to scale.

Real-World Insight: One solution couldn’t handle growth because it wasn’t designed with scalability in mind.

Recommendation: Design with the future in mind. Use modular architecture. Leverage platforms like Power Platform to connect data and support custom needs that are not aligned with your product vision or are too varied to be developed as a single feature.

Final Thoughts: Keep It Simple, Keep It Human

If there’s one lesson that stands out from all these experiences, it’s this: don’t overcomplicate the problem. Simplicity, transparency, and collaboration go a long way.

  • Engage the right people early
  • Communicate often and clearly
  • Be flexible in your process, but firm in your standards
  • And above all, treat mistakes as opportunities to improve

Digital PPM solutions are powerful, but only when they’re built with people in mind. Contact Main Digital to learn how we can help simplify your PPM journey.

Contributed By: Logan Johnson

]]>
3921