BiZZdesign HoriZZon has strong requirements for the technical aspect of things, but it is easy to start working on it if you have knowledge of VPN and UML. It gives you the chance to adapt it to your environment and to implement the things you already know.  Overall, I give it a ten out of ten.

Start simple and be consistent and understand what is the longer-term vision, as well. That way, you know what the next step is and can keep growing in that direction. If you try to start with a complex model and to capture every single piece of data that is important from the beginning, it's going to be a bit bigger task. And because you really need to start showing value, you need to start with a small amount of information and keep growing from there.

HoriZZon, is an important part of the solution. For any use case that you create, you should really create it in parallel on the HoriZZon dashboard and analyses. That will allow you to start showing the value of the information that you are putting in to a bigger community. We took slightly longer to start doing that.

My advice to new users would be to start by clearly defining your objectives when using BiZZdesign HoriZZon. While it offers a range of capabilities, including business process modeling and VPN, it excels in enterprise architecture. If your main focus is enterprise architecture, HoriZZon is an excellent choice. However, if you need specialized tools for specific tasks, ensure they integrate well with HoriZZon. So, begin with a clear understanding of your goals, and if enterprise architecture is your primary need, HoriZZon is a standout option. I would rate BiZZdesign HoriZZon as an eight, possibly an eight-plus, on a scale of one to ten. The reason for not giving it a perfect ten is the need for stronger support for REST APIs, which is vital in today's IT landscape.

Be very clear about your objectives, what you want to use BiZZdesign for. It is an enterprise architecture tool. It's not for documenting low-level designs. A good use case would be if an organization is trying to transform its overall enterprise. They obviously need to know what they currently have, where they want to go, and how they are going to get there. If these kinds of things are being discussed in your organization today, then business design tools like BiZZdesign will be very effective and valuable. But if you are only looking to document solutions, BiZZdesign might not be a good investment because BiZZdesign is very costly. You should probably look for other tools.

I will rate this solution a seven or eight out of ten, because of the missing features. I like its strong capabilities of modeling and I am impressed by the fact that it is easy to use.

I rate this solution a seven out of ten.

This tool is good for enterprise architecting. It should be used for architecting purposes only. We can derive some meaningful insights from whatever data that we have, which is the main thing.

I would rate this solution as nine out of 10.

My advice would be to scale your organization and project well, and BiZZdesign will fit your requirements.

Overall, I would rate this solution at eight out of ten.

If you're thinking of implementing BiZZdesign, take it from a capability perspective. The first and primary element to be covered is the architecture capability the organization wishes to establish. Then have your use cases defined very clearly and factor in a fair bit of time for implementation to give it time to produce results. I'd rate this solution as seven out of ten.

My advice to someone considering this solution is to follow the training. It's nice to use when you know how to use it. At first, it's good to have some explanations on how it is working. And this information is very important in order to set up your BiZZdesign environments, your libraries, typically, from an architecture standpoint, to make sure that you use it efficiently.

I know that this has been a problem at setup time, so it's not a software installation problem. It is a problem with customization. It's important to have a proper understanding of how BiZZdesign works if you want to make the right first configuration.

In the next release, I would like to see the modernization of the software.

I would rate BiZZdesign an eight out of ten. 

It's important to plan and think in advance, to be prepared in terms of what to model, for what purpose and for whom, and to prepare an internal enterprise architecture framework. Then only afterward implement it into a tool because the tool will guide you. But if you don't know what you want it's really open and customizable, but will not guide you. It's really important to work a few days or weeks on your framework and then easily implement it in the tool. 

The other advice I would give is from the beginning be in touch with C level management as a sponsor of enterprise architecture and use the reporting possibilities of the tool to satisfy them with insight into the architecture.

I would rate this solution a nine out of ten because it's really powerful and I still haven't been able to take advantage of all if its many features. 

Choose wisely. I did not take the time to investigate on other tools until now. I am willing to let Bizzdesign Architect go for a good Mac solution that also has a separation in model, views and analytics.

I would recommend it.

In the next release, I would like to see an open API.

I would rate BIZZdesign a nine out of ten.

We have now moved to a new solution that works. The most important things are stability, collaboration, and of course, the user experience. Stability is a very important part of the user experience.

I do not recommend using BiZZdesign. It is too much of a niche solution. Solutions like Enterprise Architect, or Visual Paradigm, are much more usable for the different kinds of audiences and users. For example, with Visual Paradigm, you can also model business processes and UML models.

I would rate this solution a one out of ten.