Skip to content

company-values-board.png

Concept

We have Values, Mindesets and Principles, e.g.

  • Value: Empowered Together
  • Mindeset: Own Your Impact
  • Principle: Take initiative and follow through

Company Values

Our values define how we work, make decisions, and deliver impact for our clients. They guide our behaviors every day and align our teams around a shared standard of excellence.

1. Empowered Together

  1. Own Your Impact

    1. Take initiative and follow through.
    2. If you see a problem, act on it.
    3. Communicate openly about mistakes and learnings.
  2. Grow and Help Others Grow

    1. Invest in your development and support others in theirs.
    2. Share knowledge generously.
    3. Ask for and offer feedback regularly.
  3. Deliver with Integrity

    1. Be accountable for promises and outcomes.
    2. Communicate clearly about timelines and deliverables.
    3. Admit when things go wrong and fix them fast.

How this translates to our every day work

  • What it means: Collaboration over silos; shared standards and reusable components. Knowledge flows across teams.
  • We do:
    • Use shared playbooks, templates, and naming conventions
    • Review each other's work and co-own outcomes
    • Build solutions that others can pick up and extend
  • We don't:
    • Create one-off solutions without documentation
    • Gatekeep knowledge or introduce hidden complexity
  • Signals of success: Fewer inconsistencies across projects, faster onboarding, and higher cross-team velocity.

2. Trusted Impact

  1. Create Real Value, Not Just Billable Hours

    1. Solve what matters—focus on outcomes, not outputs.
    2. Say no to unnecessary features or services, even if they're easy to sell.
    3. Be honest about what's worth doing and what's not.
  2. Earn and Keep Trust

    1. Treat client data like gold—confidentiality is non-negotiable.
    2. Be transparent about methods, limitations, and risks.
    3. Deliver consistently and communicate clearly.
  3. Be Cool, Young, and Professional

    1. Bring energy and personality to every interaction.
    2. Be approachable, but never sloppy.
    3. Use humor and creativity to build rapport, not to mask gaps.

How this translates to our every day work

  • What it means: Decisions-first analytics. Accuracy, clarity, and reliability are non-negotiable.
  • We do:
    • Favor function over form; clarity over creativity
    • Validate data logic and document assumptions
    • Design dashboards that answer real business questions quickly
  • We don't:
    • Optimize for aesthetics at the expense of readability
    • Ship work without tests or lineage clarity
  • Signals of success: Stakeholders understand and act on insights within seconds; trust remains high over time.

3. Sustainagility

  1. Build for Reuse and Robustness

    1. Write code and design concepts that others can build on.
    2. Favor modularity and clarity over cleverness.
    3. Document decisions to support future maintainers.
  2. Deliver Pragmatic Value

    1. Solve real problems with just the right level of sophistication.
    2. Avoid overengineering, but don't settle for fragile solutions.
    3. Balance speed with quality—every release should be usable and useful.
  3. Measure What Matters

    1. Track impact, not just activity.
    2. Use metrics to guide decisions, not to justify them.
    3. Reflect regularly on whether what's being built still serves the long-term vision.

How this translates to our every day work

  • What it means: Balance speed with long-term maintainability. Solve today's need without creating tomorrow's debt.
  • We do:
    • Choose simple, proven patterns (e.g., star schema, modular queries)
    • Optimize for performance and ease of maintenance
    • Invest in components that can be reused across clients
  • We don't:
    • Over-engineer or introduce fragile complexity
    • Ignore performance, governance, or documentation
  • Signals of success: Stable solutions, faster change cycles, and lower cost-to-maintain.

How We Live Our Values

  • Standards: We apply the Power BI Playbook across projects (Components, Data Wrangling, Modelling, Calculations, Visuals).
  • Reviews: We use the demo to openly discuss work done.
  • Documentation: We document lineage, decisions, and assumptions; we keep navigation and metadata clean.
  • Measurement: We track delivery quality through client feedback, reusability, and incident rates.

Behaviors to Encourage

  • Share patterns and lessons learned in team channels and in the demo
  • Keep dashboards focused on decisions and outcomes
  • Prefer reusable code and consistent structure over quick hacks
  • Make invisible complexity visible (naming, folders, lineage, comments)

Behaviors to Avoid

  • Mixing report and dataset logic in the same PBIX without reason
  • Unclear naming, hidden dependencies, or lack of ownership
  • Aesthetics over comprehension; novelty over reliability

References