In terms of the best integration architecture, what seems to me the only long-term solution is something like the unified log architecture that Jay Kreps wrote about back in 2013. All incoming writes need to go into a centralized log, such as Kafka, and then from there the various databases can pull what they need, with each team making its own decisions about what it needs from that central log. However, SuperRentalCorp has retail outlets with POS (point of sale) systems which talk directly to specific databases, and the path of that write (straight from the POS to the database) is hardcoded in ways that will be difficult to change, so it will be a few years before the company can have a single write-point. For now, each database team needs to be accepting writes from multiple sources. But a unified log is the way to go in the long-term. And that represents a large change of process for every one of those 20 teams. Which helps explain why the company has spent 2 years and $25 million trying to build an API, and so far they have failed.
Due to delays and setbacks, the deadline to launch the app in the spring of 2017 was never reached. Construction of the app only started in February 2018. In that period the current Minister of Justice and Security, Ferdinand Grapperhaus, suddenly announced that – contrary to all previous decisions – he is giving priority to the introduction of AML. Making the main function of the 112 app completely obsolete.
Strategy is hard, execution at the middle-management later is harder.
What’s missing from the story is that PARC delivered on its mission. In fact, it saved Xerox from the fate of Kodak. While its copier business was disrupted by smaller Japanese competitors like Canon and Ricoh, one component of the Star system, the laser printer, replaced the revenues lost from its cash cow and Xerox continued to grow. It also earned millions from licensing technology it invented and, it should be noted, from its investment in Apple.
Original source: The Demise of Blockbuster, and Other Failure Fairy Tales
From the referenced report:
Tax Day, April 17, 2018, the IRS experienced a storage outage due to a firmware bug on one of the IRS’s high-availability storage arrays. Because of the outage, 59 tax processing systems, including the Modernized e-File (MeF) system, were unavailable for approximately 11 hours between 2:57 a.m. and 1:40 p.m.
Storage firmware bug that hasn’t been patched.
Original source: Here’s what happened when the IRS’s electronic filing system crashed on Tax Day
“We have a small team that was tired of working this way and tired of not being able to provide this capability to our warfighters,” said Adam Furtado (pictured), chief product officer at the U.S. Air Force. “Basically, Congress told us to figure something new out.”
“We’ve been designing a brand new system to modernize for about 10 years, and we just haven’t been able to get it to the field for a ton of Department of Defense, bureaucratic and acquisitions reasons,” Furtado explained.
Original source: Transforming the Air Force into a software company with more airpower
“Many Australians, especially the poor, now see their government using digital technology as an indiscriminate, uncaring, and illegal club to beat them with. The government’s planned use of facial recognition to determine if a welfare recipient should receive benefits will do nothing to change their minds.”
Original source: Australia’s Digital Transformation Stumbles Badly
‘GAO seems to concur with the IG’s assessment. “Until NASA addresses these [IT governance] weaknesses, it will face increased risk of investing in duplicative investments or may miss opportunities to ensure investments perform as intended,” the report states.’
Must be tough for the CIO types over there with that report.
Original source: NASA faces ‘significant’ IT management weaknesses, GAO says
Original source: Gartner Survey Shows Why Projects Fail
This anecdote from a story on Sears struggles is spot on strategic thinking for most corporate meeting:
There, two mid-level employees were preparing a presentation for the CEO, Eddie Lampert, when their boss rushed in with some last-minute advice.
On a chart pad he wrote three words.
“He looks at the presenters and says, ‘Do not say these words to that guy,'” according to a former Sears executive who described the meeting to Business Insider. “That guy” meant Lampert, who would soon appear on a giant projector screen at the front of the room, beamed in live from a home office inside a $38 million Florida estate – 1,400 miles away from headquarters.
The pad with the three words was out of sight of Lampert’s video feed. One of the words on it was “consumer.”
The stakes were high. If any of those words were uttered in front of Lampert, the two presenters would “get shredded” by the CEO, whose frequent tirades had fostered a climate of fear among the company’s most senior managers, said another person – this one a former vice president.
These two and other executives say “consumer” can trigger Lampert. He wants employees to instead refer to shoppers as “members,” which is his term for customers who are enrolled in Sears’ Shop Your Way rewards program.
It was at that moment, as the executive attending the meeting watched fellow employees anxiously censor themselves in front of Lampert, that he realized he needed to flee the sinking 123-year-old company.
That perfectly captures how much energy you need to spend on seemingly ridiculous details to be successful in corporate environments, not only in caustic ones, but pretty functional ones as well. I love chronically this type of tacit corporate knowledge.
The rest of the article is great background on how older companies are struggling to modernize with plenty of anonymized sources telling gritty, but helpful stories.
This led middle managers to over promise and under deliver. One middle manager told us that “you can get resources by promising something earlier, or promising a lot. It’s sales work.” This was made worse by the lack of technical competence among top managers, which influenced how they could assess technological limitations during goal setting.
As one middle manager pointed out to us, at Apple the top managers are engineers. “We make everything into a business case and use figures to prove what’s good, whereas Apple is engineer-driven.” Top managers acknowledged to us that “there was no real software competence in the top management team”.
Who knows if that notion about Apple is true or if it causes their success. The broader point of needing to understand the unpredictable nature of software is still important. As more organizations start using and making custom written software (if only to make mobile “store fronts” to their business), knowledge of the chaotic nature of software development needs to spread more beyond IT. Even IT people get it dreadfully wrong often.
So far the best tactic we have is to redefine what “success is”: it’s not delivering everything you promised on time, but being predictable about delivering something on regular intervals. That’s a vague way of saying delivering smaller batches of code into production more often. We sort of predict/hope that this results in more useful, better software overall. We’ll see.
Now, of course, part of this process is being honest about reality. The analysis of Nokia’s failures because “management” would not accept “real talk” from their employees will kill any innovation-driven business. As the company (and RIM and countless others) shows: tech companies are never so secure that they can afford to be confident in their market position.
We thought, what if we could provide a platform for some of these independents to reach a wider audience through a research service from Gigaom? We believed that if we could pay these independents to write reports on a freelance basis, they would get the exposure of being part of a ‘virtual analyst network’ at Gigaom and we would get to tap into their expertise without having to pay the high salaries that often come with such knowledge and backgrounds. Win-win.
Including pricing, an aspect of the analyst business that I think will is key, esp. for new ventures there
We made a decision to launch at what seemed to many a ridiculously low price of $79 per year. But because we were doing something that we believe had largely never been done before, we were trying to gain significant conversion of our readership — probably around 2–3 million monthly uniques at the time — to the research product. We thought if we could make the price so low, it would enable the ‘true fans’ of Gigaom to subscribe and support while providing immense value in the form of research.
Also, this on revenue estimates:
Over time, increasing the sales and marketing mix towards research did make sense. According to an interview made by Paul, he said that research made up 60% of the company’s revenue. In the same article, revenue were estimated to be $15 million, so that translates to about a $9 million research business.