“Conquering complexity? – Yes, you can!”
Big buildings have to be managed in order to fulfil its function properly. Our client was the person responsible for making sure everything worked flawlessly in such a big building. Being the operations manager for a real estate management firm, he had to make sure that broken bulbs were replaced, air conditioners worked the way they should, and that bathrooms were cleaned according to schedule.
He wanted an application that helps him managing that.
During our first conversation, our client explained that he’d conducted quite some research: For what he was looking for, he was expecting the development of his desired application to take 5-6 months. Moreover, he knew it would cost him a fortune, before it would be as well developed as for him to be truly useful. “You can only choose two out of: good, fast and cheap”, he said, “But you can’t have all three of them.” - Yes, you can!
Most application development processes undergo a complex chain of many experts involved: The process owner explains his idea to a functional designer, who translates this to a technical designer, who talks to a data modeller, who passes it on to a programmer who receives feedback from a tester, which then goes back the chain again. On top of that, all exerts involved are often spread out across different companies and cities. Doesn’t this process remind you of the ‘whisperer game’? (remember playing this in your childhood?) Except, what comes out at the end isn’t funny at all. On the contrary, it’s extensive, takes a lot of valuable capacity, and is frustrating for everyone involved.
Yet, clients rely on highly educated (and expensive) developers to create an application that they anticipate. In the end, it remains uncertain if they get what they asked for. Our client – remember, the operations manager of a big building – didn’t. His best scenario during previous attempts, was an application with one useful function he asked for, out of three.
For our client’s purpose of managing buildings with thousands of components, the simplicity convinced him to use WEM. He decided to ask a WEM consultant to help him building the application he desired. Instead of dealing with a complex chain and many experts involved, he now communicates with only one person, the WEM consultant. Together, we developed his application in only three weeks, at a quarter of the costs he originally expected, and with all the useful functions he desired.