Many of us have spent years explaining to customers why our various versions
of Platform as a Service (PaaS) are their best alternative for customization
and deployment of business software applications. Logically, there is
little reason not to choose a PaaS as the core architecture for your
businesses software. However while there has been adoption, it hasn't
occurred at the pace which it probably should given the magnitude of the
value proposition. This of course is the quandary called "the adoption
cycle" that receives a lot of attention from authors and analysts alike.
Basically, the adoption cycle distinguishes early adopters, middle adopters
and late adopters, and put's them all on a bell curve. In technology, it is
widely thought that there is a very large gap between the early adopters and
the middle adopters, and for a company to actually overcome that g... (more)
Seven years ago we set out to build a technology that would solve the immense
problems faced by business in adoption of technology. If you are not familiar
with those problems, you need to familiarize with the now canonical Standish
Groups’ Chaos Report, which among other things documents only a 32% rate of
software projects completing successfully.
During our journey, we encountered many cool things. From the beginning, we
were early adopters of the LAMP stack; Linux, Apache, MySQL and PHP. Further,
we were able to leverage all sorts of open-source tools like WYSIWYG
controls, ... (more)
We spend a lot of time talking to business managers about how their
operations run. The perspective that we commonly face is one of "this is how
we do it; we are looking for software to do it better." But from a business
perspective, that is the wrong approach.
First, the pain of software adoption is significant, and relatively
insensitive to scope of change involved. Whether your software project is
small or extensive, employees are going to be unhappy about it for anywhere
between a couple of weeks and several months. But with all change, people
eventually adjust and move on, a... (more)
Once we understand what a good piece of business software needs to be able to
do, we have to assemble the right team to do it.
In the world of software development, there are many points where your
project can fail, and this is one of the big ones.
I have witnessed differences in developer productivity of no less than
tenfold. However, the real difference is more extreme than that because
developers who aren’t focused on your project can easily sink it.
If you are not a software developer – and even if you are – it is very
difficult to accurately gauge how long a particular task s... (more)
There are a lot of things people do in the course of a work day that can only
ever be done by a human.
Human tasks often seem too complicated to automate in a piece of software. As
a result, businesses are forced to run inefficiently when compared with, for
example, an assembly line.
But businesses that can operate more like an assembly line have a clear and
sizeable competitive advantage. Just look at your typical fast-food chain, or
a high-volume call center.
The problem is not that the rules humans follow to make decisions can’t be
automated. The problem is that identifying t... (more)