Voyansi Voices Blog

Not so long ago, coordination between team members was a major issue. Not only everyone had to adjust their schedules, but also be fully aware of the project’s latest updates and modifications. This often led to confusion, lots of hours spent in old versions of a project, and the worst part: shuffling of deadlines.

Luckily, the scenario has changed. You know about BIM360 and other cloud collaboration platforms. We all know that cloud collaboration is here to make our life easier, especially in a post-pandemic world where many employees will work from home. But what if your organization is smaller, or does not have the budget to pay for high-cost licenses? 

Last year, many of our clients and our company changed the way we worked. For our larger clients already using Bim360, there was not much of a shift other than the space's employees were collaborating from. The software allows models to be collaborated on, simultaneously, by many team members, in real-time. Changes, suggestions, and improvements no longer take long periods of time. They can be discussed and implemented in minutes, and of course, this means quicker project delivery.

It’s critically important to be able to put yourself in someone else’s shoes when having a conversation. A few years back when I was young in my career, I remember responding in a way I felt was extremely polite: “Yes Sir.” The dour look on my colleague’s face suggested I had made an error. Turns out, while this is pretty common where I’m from in Texas, it's less so in central England. The true implication of my statement was that he was old. A grave mistake coming from a 23-year-old recent college graduate just getting started in life. 

Every week, new platforms emerge to help manage every aspect of the business. There never seems like the right time to hop into something new. However, this week we'll discuss the other side. Understanding where your current software ecosystem is hurting your business. These areas can be hard to detect, especially when you've been running the same systems for years. Technical debt builds up beneath the surface, and before you know it, more agile competitors are producing things at a pace that seems like magic.

By leveraging the power of data-driven design, your team will not only come to optimal
spatial layouts today but improve your design process for the future at the same time.
Once finalized designs are manually adjusted, the feedback is sent to the repository for
future design generation.

I’m looking at a pile of paperwork on my desk this morning. I know that buried in that stack is a financial document I need to review later. I know who sent it, when it came in, and vaguely what it looks like. I’m still dreading having to physically sort through the mess to find the one piece I want. Sorry Michael Scott, but if I had one wish in life, it might be to eliminate all the paperwork. 

Imagine for a minute, you're doing laundry. Everything is dry, in a basket and ready to put away. Where do you start? In my case, following the Pareto Principle, I dump the basket on the bed and head for the towels first. Once the towels are finished, I typically start with pants, then shirts, finally folding up small things such as socks, underwear, or other accessories. 

In my last post, we covered our rules for software selection and how we found the right pieces for our software ecosystem. Choosing the software is just the beginning, stitching them into a cohesive end to end system takes trust, effort, and time. Our teams have been hard building towards new workflows. In this post, we will cover some of our design principles around our data ecosystem. These keep us aligned in our goals and allow us to decentralized our decisions.