Our architecture repository was cluttered with old and incorrect documents.
BoardWiki gives us control over our business and IT architecture.
Designs of closed projects were impossible to find.
And if found, the question was whether they were still up-to-date.
With BoardWiki we have grip on the status of every design.
Many of our projects require the collaboration of multiple internal and external teams.
We really needed an environment that can integrate multi-party designs.
We used to restrict updating our repository to the enterprise architects only.
Using BoardWiki everyone can contribute, while the enterprise architects are still in control.
Many designers find it difficult to work with formal models like UML and Archimate.
The BoardWiki model is pragmatic and gives us exacty what we need.
What is easier than sketching a brainstorm on a whiteboard?
BoardWiki proved to be much easier, as you can draft mixing new concepts with existing repository.
Our legacy applications were hardly documented.
BoardWiki reverse engineered the software for us, in exactly the same model as we use for our current designs.