How to Create a Remote Team Values Wall Using Miro Board

Miro values walls help distributed teams collaboratively define shared principles for decision-making, conflict resolution, and cultural cohesion across time zones. A visual, interactive values wall captures everyone’s input asynchronously, surfaces alignment, and creates accountability for living those values. This guide covers Miro setup, help techniques, and strategies for translating values into team norms and decision frameworks.

Why Use Miro for Remote Team Values

Miro offers several advantages over traditional methods for creating team values. Its collaborative nature means everyone can contribute simultaneously, regardless of their timezone. The visual format helps make abstract concepts tangible and memorable. Unlike a shared document that gets forgotten after reading, a Miro board remains a living reference that teams can return to and update.

Remote teams often struggle with feeling disconnected from their colleagues and company culture. A values wall that everyone helped create becomes a shared artifact that reinforces belonging. Team members can point to it when making decisions, use it to onboard new hires, and refer to it during team discussions about priorities.

Why Miro specifically (vs. Figma, Lucidchart, or Google Docs):

Infinite canvas prevents the “running out of space” feeling
Sticky notes mimic physical brainstorming (familiar interaction pattern)
Built-in visual voting and clustering tools improve the help process
Board remains accessible for future reference and updates
Free tier supports up to 3 boards, sufficient for many teams

Compared to in-person workshops: Miro’s asynchronous compatibility lets team members participate during their work hours rather than requiring everyone at the same time. Distributed teams in different timezones can add input over a few hours or days, then synchronize for the prioritization phase. In-person help would require scheduling around 5+ timezones.

Preparing Your Miro Board Setup

Before bringing your team together, you’ll need to prepare the Miro board structure. Start by creating a new board specifically for your values exercise, giving it a clear name like “Team Values Wall” or “Our Core Values.” This signals the importance of the exercise and creates a dedicated space that won’t get lost among other projects.

Set up three main sections on your board using Miro’s framing or container tools. The first section should be for brainstorming—give it a heading like “Ideas” or “Value Suggestions.” The second section is for grouping and organizing related concepts, labeled “Clustering” or “Themes.” The third section is for final values, labeled “Our Values” or “Final Selection.” This three-section structure creates a natural flow from idea generation through refinement to final choices.

Within the brainstorming section, create individual sticky notes for each team member. Use different colors for different roles or departments if that makes sense for your team, but avoid making anyone feel singled out. The goal is inclusive participation, not competitive suggestion-making.

Helping the Values Generation Session

Schedule a synchronous session where everyone can gather in the Miro board at the same time. Even though your team works asynchronously, this exercise benefits from real-time collaboration. The interaction and visible contributions from colleagues spark ideas and energy that asynchronous work sometimes lacks. Typical sessions run 60-90 minutes and should be scheduled during overlap hours when most team members are working.

Begin by explaining the purpose of the exercise to your team. Share why you think establishing explicit values matters for your remote team’s success. This context helps team members understand that their input genuinely matters and that you’re not going through a checkbox exercise. Consider sharing a brief story about a time your team made a good decision because values were aligned, or conversely, tension that arose from unclear priorities.

Pre-session preparation materials (sent 24 hours before): Share a document with sample values from other companies and brief descriptions of what each means. Examples might include: “Ownership (taking initiative without waiting for direction),” “Learning (continuous skill development and knowledge sharing),” or “Transparency (sharing information openly and early).” These examples help people understand the level of abstraction you’re looking for, though they shouldn’t constrain thinking.

Open the brainstorming section and ask everyone to contribute values they think are important. Encourage them to think about:

Behaviors they’ve seen that made teams successful
Qualities they admire in colleagues
Principles they want guiding their work
How they’d like to be treated by teammates
What inspired them to join this organization

Give everyone five to ten minutes to add their sticky notes without discussion yet. This individual thinking time prevents groupthink and ensures quieter voices get heard. Use a timer and announce “2 minutes remaining” to help people finalize their contributions.

After everyone has contributed, go through the sticky notes together as a group. Read each one aloud and allow the contributor to briefly explain their thinking. This validation matters—people want to feel heard, and having their idea acknowledged publicly reinforces that their perspective matters. During this phase, ask clarifying questions like “What does this look like in practice?” to deepen understanding.

Clustering and Organizing Values

Once everyone has contributed, move to the clustering phase. This is where the real synthesis happens. Look for values that overlap or express similar ideas. For example, “respect,” “trust,” and “transparency” might all relate to how team members treat each other. Group these together on the board.

Use Miro’s ability to draw connection lines between related items. These visual connections help the team see patterns in their values. Often, what seems like a long list of disconnected ideas reveals a smaller set of core themes when grouped together.

How to help clustering: Suggest groupings and ask if the team agrees. For example: “I see several ideas about communication style—transparency, over-communication, sharing knowledge. Should these cluster together?” Let the team refine your suggestions. This participatory approach helps everyone understand how values relate.

During this phase, encourage discussion about what makes certain values essential versus nice-to-have. Some values might feel universal—things your team couldn’t function without. Others might be aspirational—things you want to work toward but don’t always achieve. Both types have value, but distinguishing between them helps prioritize.

The clustering process sometimes reveals tensions within the team. One person might value “fast iteration” while another values “thorough review.” These tensions aren’t problems; they’re opportunities to discuss what tradeoffs your team is willing to make. Surfacing these differences openly leads to more honest and functional values.

Handling disagreements: If team members strongly disagree about whether a value belongs in one cluster or another, that’s valuable signal. It often indicates that the value’s meaning is ambiguous. Use that moment to discuss what the value actually means to different people. You might discover that “fast iteration” for one person means “shipping features quickly” while another person means “short feedback loops on decisions.” Clarifying these meanings prevents values from becoming meaningless platitudes.

Narrowing Down to Core Values

Most teams find they have twenty or thirty values after clustering, which is too many to be meaningful. The final step is narrowing down to a small number—typically five to seven values that will become your team’s core commitments.

Use dot voting or a similar prioritization technique. Each team member gets a limited number of votes, perhaps three to five, to place on the values they consider most important. This forces genuine prioritization rather than just checking everything as important.

After voting, count the results together and discuss. Sometimes the top-voted values are clear winners. Other times, you might need to discuss edge cases or values that almost made the cut. The discussion itself is valuable—it’s how the team builds shared understanding of what these values actually mean in practice.

Place the final values prominently in the “Our Values” section of your board. Use larger sticky notes or, if you’re comfortable with Miro’s design tools, create visually distinct cards for each value. Make them big enough to include a brief explanation of what the value means in practice.

Adding Context and Examples

A list of values without context rarely influences behavior. Your values wall should include concrete examples of what each value looks like in action. This is where the abstract becomes practical.

For each value, add sticky notes or text boxes with examples specific to your team and work. If one of your values is “async-first communication,” describe what that means: maybe it means defaulting to written communication, respecting deep work hours, and providing context in messages so recipients can respond thoughtfully without needing a meeting.

Ask team members to contribute real examples from their experience. What have they seen someone do that perfectly embodied a team value? These concrete stories make the values memorable and give new team members clear models to follow.

From Values to Decision Framework

A values wall becomes truly powerful when it drives actual decision-making. Without implementation, values become motivational posters on the wall—noticed during onboarding, forgotten in daily work.

Create a decision filter based on your core values. When your team faces a choice (technology selection, hiring decisions, process changes), explicitly reference values during discussion. For example: “We value transparent communication, so let’s document the reasoning for this decision and share it with the team, not just announce it.” This grounds conversations in shared principles.

Document 2-3 concrete decisions your team has made using your values. Examples:

Why you chose async-first communication (aligned with your “respect for deep work” value)
How you decided to maintain a smaller team rather than hire quickly (aligned with “sustainable pace” or “quality over speed”)
Why you open-sourced parts of your codebase (aligned with “learning” and “community”)

These real-world examples make values tangible and show that they actually influence decisions.

Once your Miro board is complete, export or document the values somewhere permanent. Miro boards can be exported as PDFs or images, but also consider adding your values to a more accessible location like a team handbook, wiki, or company documentation.

Create a brief summary document (one to two pages) that explains:

How your team arrived at these values (the process)
Who participated and when the session occurred
The five to seven final values and brief explanations
One or two examples of each value in action
How the team will use these values in decision-making

This documentation helps future team members understand not just what the values are, but why your team chose them. New hires especially benefit from seeing the reasoning behind values—it helps them assimilate more quickly.

Miro board best practices for sharing:

Create a read-only shared link for team reference
Pin the board to your team Slack channel or wiki
Use the board’s presentation mode during onboarding sessions
Keep the board updated as values evolve (never archive it)

Share the Miro board link widely and reference it regularly. Values only matter if they inform daily work. When making decisions, ask “which value applies here?” When onboarding new team members, start by sharing the values wall and discussing what each value means to the team. Record a 5-minute video walkthrough of your values board and include it in onboarding materials.

Using Values in Decision-Making

Create a decision filter that explicitly references values during important team discussions:

Hiring decisions: Which candidate embodies our values? If one value is “continuous learning,” you might prioritize candidates who’ve invested in skill development. If another value is “mentorship,” you might prioritize candidates with teaching experience.

Feature prioritization: Does this feature align with our stated values? If your team values “low cognitive load for users,” you might reject a feature with powerful functionality but steep learning curve.

Process changes: When considering shifting from synchronous to async standups, reference values: “We value asynchronous communication and respect for deep work. This change aligns with both.”

Conflict resolution: When two team members disagree, reference values to find common ground rather than arguing positions.

Performance and promotion decisions: Values guide who gets promoted into leadership. If a value is “enabling others,” someone who accumulates individual contributions but doesn’t mentor teammates might not be the right promotion candidate. Conversely, someone building team capability aligns with that value.

Maintaining and Evolving Your Values Wall

Technical Setup in Miro

For teams new to Miro, a quick setup refresher:

Creating the board: Start with blank board. Add a title: “Team Values Wall”
Organizing sections: Use Miro’s frame tool to create three labeled sections: “Brainstorming,” “Clustering,” “Our Core Values”
Adding sticky notes: In brainstorming section, create different color sticky notes for each person (optional but helps track contributions)
Setting up voting: After clustering, use Miro’s dot voting feature or add voting stickers in the “Our Core Values” section
Finalizing documentation: Create a text box listing final values with descriptions for future reference

Miro’s infinite canvas prevents the “running out of space” problem that Google Docs or Figma might present. Teams can expand sections as needed.

Teams change, and values may need to evolve over time. Schedule periodic reviews of your values wall—perhaps quarterly or semi-annually—to check whether the values still resonate. Remove values that no longer feel relevant, add new ones that emerge as important, and update examples as your team evolves.

Miro makes this easy because the board remains a living document. You can add new sticky notes, move things around, and update examples at any time. Treat your values wall as a reference document that grows with your team rather than a fixed artifact from a single moment.

Tips for Remote Teams Using Miro

A few practical tips can make your Miro values session more successful. First, ensure everyone has a Miro account and knows basic Miro navigation before the session. Technical difficulties waste valuable collaborative time.

Second, consider time zones when scheduling. Try to find a time when the maximum number of team members can attend synchronously, even if that means someone joins very early or very late occasionally. The value of real-time collaboration often justifies this inconvenience.

Third, assign a facilitator who can keep the discussion on track. Without someone guiding the process, conversations can drift or certain voices can dominate. The facilitator’s job is to ensure everyone contributes and the team makes meaningful progress.

Finally, make it enjoyable. Values creation should feel like a celebration of what makes your team great, not a bureaucratic exercise. Play some music, start with positive stories about the team, and acknowledge the effort everyone is putting into making the team better.

Automate Async Standups via Slack Bot

import os
from slack_sdk import WebClient

client = WebClient(token=os.environ["SLACK_BOT_TOKEN"])

def post_async_standup(channel: str, update: dict) -> None:
    """Post a structured async standup to Slack — no live meeting needed."""
    text = (
        f"*Yesterday:* {update['yesterday']}\n"
        f"*Today:* {update['today']}\n"
        f"*Blockers:* {update.get('blockers', 'None')}\n"
        f"*Timezone:* {update.get('tz', 'UTC')}"
    )
    client.chat_postMessage(channel=channel, text=text, mrkdwn=True)

# Each team member calls this from their own bot script or slash command
post_async_standup(
    "#standup-eng",
    {
        "yesterday": "Shipped auth service migration",
        "today": "Write integration tests",
        "blockers": "Waiting on @alice to review ADR-042",
        "tz": "UTC+8 / Singapore",
    },
)

Built by theluckystrike — More at zovo.one