Minimise the tentacles on the OctopOSS. Keep it simple
“Today’s consumers want to get the best prices, but offering your brand at a discount can undermine profits and threaten viability. Smart brands utilize strategies to create and sustain a meaningful difference that helps consumers justify spending more.” Nigel Hollis, in his PoV on branding. I once read a statistic that at one point Apple […]
OSS delivery teams can be quite tense environments to work within can’t they? Deadlines, urgency, being in the customer’s line of sight and did I mention deadlines? [As an aside, I’m not sure which type of deadline is more stressful, the ongoing drain of fortnightly releases under Agile, or the chaos of a big-bang release […]
“The cloud model (ie hosted by a trusted partner) becomes attractive from the perspective of repeatability, from the efficiency of doing the same thing repeatedly at scale.” From, “I want a business outcome, not a deployment challenge.” OSS struggles when it comes to repeatability. Often within an organisation, but almost always when comparing between organisations. […]
“Flow, also known as the zone, is the mental state of operation in which a person performing an activity is fully immersed in a feeling of energized focus, full involvement, and enjoyment in the process of the activity. In essence, flow is characterized by complete absorption in what one does, and a resulting loss in […]
“I often leverage use-case design and touch-point mapping through the stack to ensure that all of the use-cases can be turned into user-journeys, process journeys and data journeys. This process can pick up the high-level flows, but more importantly, the high-level gaps in your theoretical stack.” Yesterday’s blog discussed the use of use cases to […]
When it comes to designing a multi-vendor (sometimes also referred to as best-of-breed) OSS architecture stack, there is never a truer saying than, “the devil is in the detail.” Oftentimes, it’s just not feasible to design every interface / integration / data-flow traversing a theoretical OSS stack (eg pre-contract award, whilst building a business case, […]
Back in early 2014, PAOSS posted an article about the importance of closed loop designs in OSS, which included the picture below: It generated quite a bit of discussion at the time and led me to being introduced to two companies that were separately doing some interesting aspects of this theoretical closed loop system. [Interestingly, […]
“We can look and take lessons on how services evolved in the cloud space. Our customers have expressed how they want to take these services and want a business outcome, not a deployment challenge.” Shawn Hakl. Make no mistake, cloud OSS is still a deployment challenge (at this nascent stage at least), but in the […]
“Just because you’re afraid of doing something doesn’t give you a permission slip to not do it.” Debbie Millman. There’s a lot of fear in OSS. So many things can go wrong (the OctopOSS theory), so much incompetence is created, so many nearly insurmountable integration challenges await and their complexity means that there is no […]
“Here are a few questions I reflect on: – Am I excited to be doing what I’m doing or am I in aimless motion? – Are the trade-offs between work and my relationships well-balanced? – How can I speed up the process from where I am to where I want to go? – What big […]
“When in doubt, connect. That’s what fast-growing, important organizations do. Making stuff is great. Making connections is even better.” Seth Godin in his post here. Simple words. Simple concept. Interesting message…. with a traffic-light of OSS layers. Layer 1 – A connection red light The more connections an OSS has, the more enriched the data […]
There’s an interesting thing with off-the-shelf OSS solutions that are subsequently highly customised by the buyer. I call it the trickle-down effect. By nature, commercial-off-the-shelf (COTS) solutions tend to be designed to cope with as many variants as their designers can imagine. They’re designed to be inclusive in nature. But customised COTS solutions tend to […]
Reports are an important interaction type into any OSS, obviously. What’s less well observed is the time (ie cost) it can take to create and curate canned reports. [BTW in my crude terminology, Canned Reports are ones where the report format and associated query is created / coded and designed to be run more than […]
When planning out a full-stack business / network / services management solution, I tend to follow the top-down, bottom-up design process. Let’s take the TMN pyramid as a starting point: Image courtesy of www.researchgate.net Bottom-up: When designing the assurance stream (eg alarms, performance, etc), I start at the bottom (Network Elements), understanding what devices exist […]
“The Mechanical Turk… was a fake chess-playing machine constructed in the late 18th century. From 1770 until its destruction by fire in 1854 it was exhibited by various owners as an automaton, though it was eventually revealed to be an elaborate hoax. The Turk was in fact a mechanical illusion that allowed a human chess […]
“If [more] information was the answer, then we’d all be billionaires with perfect abs.” Derek Sivers. The sharing economy has made a deluge of information available to us at negligible cost. We have more information available at our fingertips than we can ever consume and process. So why don’t we all have massive bank balances […]
OSS can be complicated beasts with many tentacles. It can make starting a new project daunting. When I start, I like to use a WBS to show all the tentacles (people, processes, technology, contracts) on a single page, then look for the lead domino (or dominoes). A lead domino is the first piece, the one […]
In 1998 Berkshire Hathaway acquired a reinsurance company called General Re. “The only significant staff change that followed the merger was the elimination of General Re’s investment unit. Some 150 people had been in charge of deciding where to invest the company’s funds; they were replaced with just one individual – Warren Buffett.” Robert G. […]
During the last week, this blog-roll has talked about the benefits, but also the challenges facing implementation techniques like Agile in the world of OSS. There’s no doubt that they’re good at breaking down challenges into smaller pieces for implementation. Unfortunately there’s also the risk of doing for the sake of doing – stuffing more […]
What does the integration map of your OSS suite look like? Does it have lots of meatballs with a spaghetti of interconnections? Is it possibly even too entangled that even creating an integration map would be a nightmare? Similarly, how many customisations have you made to your out-of-the-box tools? In recent posts we’ve discussed the […]
