Featuring: Lucas Charello, Senior Board Consultant at Kiwika and Community Captain.
One phrase comes up often in Board EPM sales conversations: “You can build anything you want.” It reflects one of Board’s greatest strengths, but without the right discipline, that same flexibility can become a source of complexity.
Board enables customers to design custom workflows, model unique planning processes, and reflect on the way their business truly operates. That flexibility is a major reason the platform is trusted by leading multinational organizations and has been recognized as a Gartner Magic Quadrant Leader for the fourth consecutive year.
Experienced customers and consultants also recognize that this flexibility delivers the greatest value when it is guided by clear priorities and strong implementation expertise. As one customer put it, “The flexibility of Board is impressive, but it can also be dangerous because it encourages us to build every minor detail into the planning process.” Another customer recently noted selecting the right consultants for the first project is one of the most important moments in a Board digital transformation: “Once we find the right people, we keep them.”
These perspectives come from satisfied customers, and they point to an important implementation principle: Board’s greatest strengths create the most value when they are paired with focus, governance, and experienced guidance.
From Unlimited Flexibility to Purposeful Design
Flexibility transfers a specific burden onto the project team—the burden of knowing what not to build. More opinionated EPM tools protect customers from themselves by imposing constraints — frustrating during implementation but disciplining over time. Board imposes remarkably few constraints. Every department can have its custom allocation logic, its bespoke workflow, and its own reporting template. Each individual request may be reasonable on its own, but, without clear prioritization, their combined effect can turn an application into a labyrinth. Over time, that complexity can extend timelines, increase costs, and make it harder for customers to realize value quickly.
Four Areas Where Focus Protects Flexibility
- Scope growth that feels like progress: In a Board implementation, adding complexity looks like using the platform correctly. When a new workflow can be configured in one day, asking for three more is easy to justify. The cumulative effect — more dimensions, more calculation rules, more custom screens — is a system no one fully understands and few can maintain. EPM experts consistently flag this: Builds containing far too many exceptions and particular cases generate models that are complex and difficult to maintain instead of streamlined and improved. It often happens when builders try to replicate existing Excel models exactly.
- The "garbage in, garbage out" problem, amplified: Board's flexibility means more places to introduce logical errors, more calculation layers to debug, and more custom structures to validate. When account codes are inconsistent across business units or consolidation rules aren't standardized before go-live, the result is inaccurate reports produced by a system too complex to audit. The richer the build, the higher the data quality bar required to make it reliable.
- Administration complexity that outlasts the project team: Consultants build the application, then move on. Because every Board environment is genuinely unique, there is no generic documentation that describes yours. Internal administrators inherit something they cannot fully reconstruct, or at least not easily.
- The gap between developers and end users: Board’s flexibility can be especially powerful for the people designing the solution, but the experience of end users still needs to remain central. When the interface feels counterintuitive, users may create workarounds such as shadow spreadsheets, manual reconciliations, or data exports that are manipulated outside the platform. The cruel irony: months of implementation effort can produce a system that users actively avoid, returning the organization to the fragmented processes Board was meant to replace.
What Good Board Implementations Have in Common
Successful Board implementations tend to share six disciplines: clear objectives, simplified processes, strong collaboration between functional experts and builders, maintainable design, change management, and phased rollout.
- They define success before they define the build. Measurable objectives drive every architectural decision, and new requirements are tested against the question "Does this serve the objective?" rather than "Can we build it?".
- They resist replicating legacy processes, treating Board as an opportunity to redesign planning rather than perpetuating existing inefficiency.
- They establish a good synergy between Board builder and functional expert, where the latter express the core business needs effectively and the former brings up options, always advising the customer away from low added value with high time-consuming builds.
- They build for maintainability from day one, documenting as they go, adding comments everywhere in the code and designing for the administrator who will manage the system without the original developer's help.
- They invest in change management, recognizing that the most sophisticated environment fails if end users don't adopt it.
- They phase the rollout, proving value in one process or business unit before expanding. Compounding mistakes across an entire enterprise is far harder to recover from than a contained and correctable pilot.
Turning Flexibility into Lasting Value
Board EPM is an exceptional platform, and its recognition across Gartner, BARC, and peer review communities is well-deserved. But exceptional platforms demand exceptional discipline. Board's flexibility is a genuine strength, not a challenge. The challenge lays in the absence of a governance framework to guide it.
Most of the time, when the project team builds an overly complex or disjointed application, the customer ends up paying for it twice — the first time to build it and the second to simplify it. User adoption drops as well as the team’s credibility. Steering the customer toward lean, high-value builds is a consultant’s core responsibility. That includes challenging requests that would create more complexity than value.
The goal in enterprise planning is never to build the most sophisticated system. It is to build one that people trust, use, and rely on to make better decisions. A successful Board implementation should simplify planning, strengthen alignment, and give teams greater confidence in their data and processes.
Consultants who understand this become more than implementers. They become decision architects, bridging the gap between technology and business impact. With the right discipline, Board’s flexibility becomes a powerful foundation for better planning, stronger adoption, and more confident decision-making.
