Is hard return on investment all there is? In exploring business (and tech) projects, we have a tendency to think about the immediate, quantifiable ROI. Yet, there are times when the soft costs or other benefits outweigh any measurable ROI, and sometimes are even worth a negative ROI... in the short term. This was highlighted to me again yesterday. A colleague of mine is heading up a project to move tens of thousands of VMs from on-premise to the public cloud.

One of the hot words over the last few years has been "Bimodal IT". I won't go into a complete definition - let's leave the people who make much money off of the idea to explain it. The short form is that some technology activities are more traditional, sequential and driven by a focus on safety, while others are more innovative, agile and driven by a focus on new risks.

At the Container Summit, I was speaking with a colleague at a booth, when a potential customer of his walked up and engaged in conversation. He asked an interesting question: How do I know if my software is ready for the cloud or for containerization? While an interesting discussion ensued about the company's technology, the most important points of the conversation were three key lessons: Just about any software or application can be containerized.

Earlier this week, I had breakfast with a colleague of mine from Rancher. Rancher is a great "orchestrator" for Docker containers. I have recommended and used them in production environments. Containers - one of the hottest technologies in the last year - is a much more efficient form of virtualization than traditional "hardware" virtualization (think VMWare or Xen), while providing a superior application distribution model. The challenge is that while the native Docker tools are pretty good for managing individual servers with containers, managing more than a few containers, let alone across more than a few servers, becomes impossibly complex.

Steve Denning has a great short article in Forbes, referencing Peggy Noonan on what Steve Jobs had to say about why big companies fail. The article is worth reading - actually, the entire Isaacson biography of Jobs is a great read - but here is the money quote: The company does a great job, innovates and becomes a monopoly or close to it in some field, and then the quality of the product becomes less important.

In the last week, I have had several discussions with some really smart technologists, partially focused on what makes technology companies nimble and fast and, therefore, great. In the last article, we discussed hiring 10x people, and especially the way many great employees compound together to create up to 2 orders of magnitude faster companies. However, hiring really smart employees is necessary, but it is not sufficient. What these employees need is independence.

If you want to change technology that requires a change in process or, more seriously, culture, then you need to change the culture first. Get your people on board and then make the changes. Right? Perhaps not. Or at least not always. If your culture is flexible and open, people collaborate across groups and you are staying competitive, then, yes, change some of the culture to new ways of working, then adopt new technology that requires the different mindset.

Although the title for this article might imply suggestions for Proctor & Gamble's IT department, instead we will address how badly code can "smell" and how and when to prevent it. In business as in software, the concept of a "smell test" is a base instinct for if something is a bad idea or implementation: if something smells bad, it probably is. One of my favourite technology bloggers, Adrian Colyer, wrote a recent article about a fascinating analysis of open-source projects, primarily Apache, Eclipse and Android.

Over the last week, I have had several discussions about the challenges to successful outsourcing. One person was dealing with manufacturing products in China; another was managing outsourced server maintenance and operations; yet a third had a financial technology management service provider. In all the cases, the question was the same: how do you know when it is good to outsource, and how do you make it succeed? Successfully outsourcing anything is far beyond the scope of a single article.

What do you do when you want to move towards more rapid deployment, perhaps as close as possible to continuous delivery, but the culture and incentives push against it? This is the exact issue I have had at several clients over the years. When brought in to improve their operational performance, I found that, with all of them, a major issue was instability due to deployments. The flow looked something like this:

The Internet has been abuzz for the last week about a hitherto little-known clause in Samsung's "Smart TV" privacy policy. The news was most prominently covered in the Daily Beast, here. The Daily Beast includes a link to the entire privacy policy, but the important element is: Please be aware that if your spoken words include personal or other sensitive information, that information will be among the data captured and transmitted to a third party.

What would you call a global, enormous, Fortune 500 company that 95 out of 100 of its employees strongly recommend it as a place to work? Sure, an exciting new startup, but an old-school 70-year old company? What if that company was IBM? In a great article by a former IBM manager, he explains how they used to have: Merciless manager reviews Managers much younger than their employees who took severe criticism from those employees.

Continuing our series on cloud services, especially our most recent one, "How to Do True Cloud", we now turn to the technology that enables true cloud services. This article will go more in depth than the previous ones; after all, we are discussing technology services. However, it will not go so deep as to lose the business-side executives. Indeed, any great executive in technology needs to hold to two principles simultaneously:

"The purpose of a business is to create and keep a customer." - Peter Drucker No matter how many times we say it, we forget it. We get caught up in operations, or competition, or marketshare, or share price. Yet a business, like a life, has a purpose: to create and keep a customer. I might add, "to keep that customer profitably satisfied." Earlier this month, a very well known Apple developer, one of the "

Apple's philosophy for technology is, "just make it work." I had one of the early pre-iPod mp3 players. It was a great piece, lots of battery life, played every format out there at the time... and within a year I had replaced it with an iPod. Transferring music to this player and managing it was just an enormous headache. With iTunes and iPod, it "just worked". Fast forward to the year 2014.