www.anothertrail.com https://www.anothertrail.com AnotherTrail, Innovation in exposing new technologies Tue, 04 Dec 2018 12:10:03 +0000 en-US hourly 1 https://wordpress.org/?v=4.9.9 Heritage Sales – Wash Whites Separately https://www.anothertrail.com/archives/74499 https://www.anothertrail.com/archives/74499#respond Tue, 04 Dec 2018 12:10:03 +0000 https://www.anothertrail.com/?p=74499 Tradition dictates that during one’s teenage years, a parent will take you to one side and explain the fundamentals of the humble washing machine. Read the label, check the temperature to avoid shrinkage and above all else don’t mix whites and colours. Red socks and a white shirt equals pink shirt and much sorrow my son.

For decades the IT industry has followed similar rules, the physical infrastructure is king, has many different silos and should be kept separated from applications.

But then some creative people saw a business model in pink shirts.

Today the cloud and associated virtualisation give the agile end users infinite colours and sizes, with an invisible infrastructure on a pay-as-you-use basis supported by code hungry Devops teams crafting a 24 hours stream of ingenuity and profit.

Someone said ‘If your business can be disrupted by a software company then you are a software company and if you don’t adapt you soon will die’. But the majority in our industry were born to wash whites separately and the transition can be painful and more importantly slow.

Sure enough, a vendor can hire bright young things to craft a Cloud based offering to accommodate both Virtual Private Cloud(VPC) and Cloud Native requirements, yet that must be marketed and sold before its value can be realised, and hence the journey along the Amazon begins.

Firstly, they must navigate the rapids, the speed of a Cloud Native business environment both in terms of end-users drivers and new routes to market. The concept of a Citizen Integrator bypassing a traditional Systems Integrator and servicing his/her needs direct via a SaaS marketplace, radically changes product and service positioning.

Then consider the traditional rip and replace capex centred Vendor+VAD+VAR model. It simply does not work in a pay-as-you-use virtualised Cloud based IaaS, SaaS, PaaS environment. The whole fiscal mechanics must adapt to a new and more flexible income stream.

How does a traditional VAR migrate towards the cloud world and engage in a $80bn(and growing) SaaS market?

AnotherTrail has been working on exactly this question and how through new and innovative technology we can all sell pink shirts.

https://www.anothertrail.com/archives/74499/feed 0
Edge-Computing & SD-WAN https://www.anothertrail.com/archives/74495 https://www.anothertrail.com/archives/74495#respond Sun, 04 Nov 2018 14:31:38 +0000 https://www.anothertrail.com/?p=74495 What many companies start to advise, we need Edge Computing. Right but..

Most refer to the new challenge: Establishing last-mile connections. Users, and by extension their devices, are always on the move and are constantly connecting to different Internet Service Providers (ISPs). Building robust, reliable connections in a global market that enables a service to connect with all of the ISPs in a region is time-consuming, expensive, and can be a major distraction for an organisation that needs to focus on other business-critical issues. Solution: organisations can look for established and comprehensive network of last-mile service providers to efficiently service end users.

AnotherTrail’s view

This is where SD-WAN has a bright future, with smart policy management end2end, ie. from the CPE (Customer Premises Equipment) to the back-end Datacenter. The architecture will look like described below:


Back-end DC———————-Front-end DC—————————Client CPE and data sources

Most likely a public Cloud                 Most likely a Telco DC                          Most likely an architecture with Sensors, Data appearing suddenly

Typically the old PoP

Technologies like Plexxi (Fabric as a Service, now part of HPE) will be used between the DCs, ideally up to the CPE if fibre @ 10G is available, else SD-WAN will play the last mile, enabling to reach the front-end DC with which ever last mile ISP and combination of ISPs.

Integrating SD-WAN with Fabric-as-a-service is the enxt big topic. With a software-defined workload distribution leveraging application & latency policy management.

Who will be the 1st to deliver such?



https://www.anothertrail.com/archives/74495/feed 0
Software-defined charging https://www.anothertrail.com/archives/74489 https://www.anothertrail.com/archives/74489#respond Tue, 16 Oct 2018 12:49:56 +0000 https://www.anothertrail.com/?p=74489

Electrically charged employees

In my agile world of continuous improvement, sprints and microservices, I demand a responsive and communicative management structure, receptive to the needs of the business, their customers and employees.

I need a creative interactive work environment that enables the development of ideas, team spirit and individual interactions. Space to work, space to play, space to rest, indeed a space where we feel at ease and in which we can deliver the best result for the business.

…and we also drive electric vehicles, so I need on-premise charging across all company locations plus single app based control and account management.

The pain

The average time spent filling up at a petrol station is 7 minutes. At a charging point a Tesla Model 3 will takes approximately 6 hours. Therefore, to remove the employees fear of ‘Have a got enough charge/power to get home’, individual businesses and landlords need to accommodate on premise Electric Vehicle Charging.

The same is true for Park and Ride, Retail, Hospitality etc, but is EV Charging an extra complication or a new opportunity?

From an installation standpoint it would be about parking space, available power/cabling, planning permissions and forecast growth. You could treat each deployment as an isolated service, indeed many of the initial offerings are just that, leading to the EV Drivers number one complaint, ‘Multiple App’ syndrome, one for each deployment/vendor.

But standards are emerging and with them comes opportunity to develop Cloud based generic service solutions in the same way we consume Wifi.

The standards

The first of these standards is the Open Charging Point Protocol delivering open and interoperable communications protocols for the EV charging infrastructure supporting all the functionality needed for advanced charge management.

The second is OpenADR. Some suggest by 2040 EVs will use 5% of the entire Western European power generation. Against that prediction Open Adaptive Demand Response standard bridges the gap between the power providers and the operators to collaboratively manage load/demands, special offers and reporting.

Combine OCPP and OpenADR into a single cloud based solution and things get interesting, but who could benefit?

The Driver: Could utilise a single application for all his/her EV charging needs, including payment and when linked into ‘API Clearing house’ services could map location to local hotel, restaurant and public transport offerings.

The Owner/Businesses: Suddenly the premises become far more attractive whilst front facing multi-tenant software allows for special charging rates for employees, guest etc.

Added to this is improved operational management of individual charge points across the entire estate.

At the back-end sit the Utility company and an ever greater need to manage energy consumption, eventually in real time. Open ADR provides this interface with owner and Utility collaborating to deliver suitable efficiencies.

The Utilities: Seen as ultra conservative, early interactions with Cloud based services appear to be limited to usage reporting, but with increased demand, Open ADR offers a conduit to more complex load management and service delivery.

At AnotherTrail we work with EVConnect http://evconnect.comto develop their European partner and end-user footprint and also integrate with other service related technology to augment and enhance service levels.

In an agile world, software defined electric vehicle charging will enable the electrically charged employee.

https://www.anothertrail.com/archives/74489/feed 0
Optimising Cloud spend https://www.anothertrail.com/archives/74484 https://www.anothertrail.com/archives/74484#respond Wed, 26 Sep 2018 13:17:43 +0000 https://www.anothertrail.com/?p=74484 Optimising Cloud spend

The Great Wall still survives, a technology dividing line between those weaned on SLAs and 5x9s and those emerging from the Cloud Native Design to Fail cocoon, fluttering the wings of network invisibility and ‘just code and launch’ mindset.

Whilst these two camps are miles apart they suffer one common blind spot, one pivotal flaw in the general scheme of things, namely the lack of technical accounting.

Back in time tales abound of 2Mb circuits running to abandoned facilities, serving no one, devoid of organisational responsibility yet leaving confused finance officers with hefty annual charges to pay. Happy days. Fast forward to public cloud compute, be it VM or Docker, and witness CFO’s operating with little or no visibility of what they are spending their cloud budget on.

A diligent operations person would point to inherent services like AWS Tagging, but does that scale?  Equally solutions linking dynamic IP address harvesting into a cmdb with application definitions.

However, even if diligence prevails how do you optimise agile development requirements against available public compute offerings and associated cost models? Can resource brokers also play their part in reducing upfront deposits on elements like reserved instances?

Anothertrail have built a technical accounting reference model of vendors both commercial and open source, which when implemented addresses the cost concerns and provides detailed planning of computation resource and optimisation against an agile development environment.

This compliments our Cloud migration model covering IPAM, Packet level visibility, automation and service assurance.

https://www.anothertrail.com/archives/74484/feed 0
Facts about Innovation -Extract from an MIT Review article https://www.anothertrail.com/archives/74448 https://www.anothertrail.com/archives/74448#respond Mon, 03 Sep 2018 06:53:23 +0000 http://www.anothertrail.com/?p=74448 Innovation Insight 1

Innovation isn’t necessarily about new things; it’s about new value.

Innovation isn’t just about developing new products or technologies. In a 2006 MIT SMRarticle “The 12 Different Ways for Companies to Innovate,”1 Mohanbir Sawhney, Robert C. Wolcott, and Inigo Arroniz encouraged executives to think broadly about what types of innovation are possible. The authors noted that companies within the same industry “tend to innovate along the same dimensions” — whether those dimensions are research and development (R&D), process innovations, or branding. Viewing innovation too narrowly, the authors pointed out, “blinds companies to opportunities and leaves them vulnerable to competitors with broader perspectives.” Sawhney, Wolcott, and Arroniz used examples such as Starbucks, which initially innovated not by producing a different product but instead by creating a different kind of customer experience — what the company termed a “third place” for gathering that was between home and work.

Business innovation, the authors stressed, has to do with new value, not necessarily new things — and comes in many flavors. The authors presented an “innovation radar” so companies can consider 12 different areas in which they might innovate — ranging from method of value capture to operating processes to platforms. “When a company identifies and pursues neglected innovation dimensions, it can change the basis of competition and leave other firms at a distinct disadvantage,” the authors concluded.

Innovation Insight 2

Challenge competitors by playing a different game.

Technological disruption is one way to upend a market, but it isn’t the only way. For some companies, the secret, according to Constantinos Markides of London Business School, is to change the rules of the game.

In researching his 1997 article “Strategic Innovation,”2 Markides studied more than 30 companies that had successfully attacked leaders in their industry without the benefit of a breakthrough technological innovation. The common element in such successes, Markides found, was that the attacker changed the rules of the game, a phenomenon he termed “strategic innovation.” For example, Southwest Airlines changed the rules of the airline industry when it chose to fly its planes point-to-point rather than through hub cities. “Strategic innovation occurs,” Markides wrote, “when a company identifies gaps in the industry positioning map, decides to fill them, and the gaps grow to become the new mass market.”

Markides offered a framework for thinking about strategic innovation that’s grounded in three basic questions: Who are your customers? What products or services should you offer them? And how should you offer them? To change the rules of the game in their industry, Markides noted, companies can either redefine the business, redefine who their customers are, redefine what they offer customers, redefine how they do business, or start the strategic thinking process at a different point — for example, the organization’s unique capabilities.

Of course, coming up with new ideas for strategic innovation does not guarantee success. “It’s worth reemphasizing that coming up with new ideas is one thing; succeeding in the market is another,” Markides wrote.

Innovation Insight 3

Focus on identifying and resolving uncertainties in innovation projects.

Breakthrough innovation projects necessarily involve a high degree of uncertainty, Mark P. Rice, Gina Colarelli O’Connor, and Ronald Pierantozzi observed in their 2008 article, “Implementing a Learning Plan to Counter Project Uncertainty.”3 So, rather than try to apply disciplined planning techniques to such innovation projects, they proposed that companies focus on identifying and prioritizing the uncertainties that need resolution.

The authors developed a framework for turning uncertainty into learning by studying large innovation projects at 10 technology-intensive companies, including GE and IBM, over a period of seven years. They concluded that, in breakthrough projects where the shape of the future market has yet to be determined and where it’s unclear which applications will succeed, identifying milestones to achieve may not be the best approach. “In such scenarios,” Rice, O’Connor, and Pierantozzi wrote, “it is more reasonable and useful to identify and prioritize uncertainties that must be resolved, to define alternative approaches to exploring them, and to continually assess the value of cumulative learning compared to the costs incurred.”

Rice, O’Connor, and Pierantozzi suggested that companies develop what they call a “learning plan” to help teams examine four types of uncertainty: technical, market, organizational, and resource. Managers can use the process, the authors wrote, “to uncover gaps in knowledge and create a record of what is known, to prioritize which uncertainties are most critical and propose alternative assumptions about the reality behind each uncertainty, and to find ways to test assumptions and resolve the uncertainties as quickly and inexpensively as possible.”

The authors provided some helpful suggestions about how to apply their approach effectively. Rather than approaching the process in a linear fashion, they called for multiple passes, or “learning loops,” to allow teams to review results, clarify assumptions, and identify new tests to initiate. A critical aspect of the approach, they argued, is proper oversight by people with experience in highly uncertain projects. One risk of using people without such experience is that they may kill promising projects too early.

Innovation Insight 4

Remember that being first to market is no guarantee of success.

One of the most enduring axioms of business is that, irrespective of whether you’re running a startup or an established company, it pays to be first to market. But as authors Gerald J. Tellis and Peter N. Golder explained in a 1996 article titled “First to Market, First to Fail? Real Causes of Enduring Market Leadership,”4 the case for entering the market before anyone else can be — and often is — overstated and distorted by the nature of the data. The authors pointed out that previous studies finding that pioneering companies gained an advantage had only surveyed surviving pioneers.

The authors studied the history of 50 consumer product categories and found that pioneering companies had a high failure rate: 47%. Importantly, the authors found that being a market pioneer was less advantageous from a market-share perspective than being what they called an early leader, one who enters the market after pioneers but becomes a leader in the market’s early growth phase. Early leaders, the authors wrote, tend to have low failure rates and significantly higher market shares than pioneers.

Tellis and Golder found that the early leaders they studied excelled in comparison to pioneers on five factors. Early leaders had a “vision of the mass market” for the product; they persisted through business challenges; they were able to commit resources in line with their vision; they innovated relentlessly, even if it meant risking (or cannibalizing) their other products; and they leveraged their assets. In the disposable diaper market, for example, a well-reviewed product called Chux predated Procter & Gamble’s 1961 introduction of Pampers by decades. But P&G managed to leverage its technical and financial resources to build a position in the mass market. Likewise, in the U.S. market for light beer, several products predated the introduction of Miller Lite in the 1970s. To build market share for Miller Lite, its parent company was willing to spend heavily on advertising (something one of the market pioneers, Gablinger’s, didn’t do).

The takeaway, Tellis and Golder concluded, isn’t that it’s better to be a follower than a pioneer. It’s that paying attention to the five leadership factors will have more impact on long-term success than whether or not you enter the market first. “Being first,” they wrote, “does not automatically endow an advantage; it only provides an opportunity.”

Innovation Insight 5

Let your customers develop your next product.

When developing new products, how do you determine what customers want and what they need? This, of course, is a classic challenge, one that managers have labored over for many years. But in a 1977 article titled “Has a Customer Already Developed Your Next Product?5 Eric A. von Hippel of the MIT Sloan School of Management pointed out that many companies fail to take into account critical information that’s available to them. In studying manufacturers of scientific instruments and process equipment, von Hippel identified a pattern: “Most of the innovative products commercialized in those industries were invented, prototyped, and used in the field by innovative users before equipment or instrument manufacturing firms offered them commercially.” Von Hippel found further that “the manufacturer who takes advantage of user efforts needs only to contribute product engineering work to obtain a first-to-market product innovation.”

Users are willing to do innovation work and provide valuable information, von Hippel wrote, if they need the new product “as much as or more than you do.” This can save companies a good deal of money. A big challenge, though, is convincing internal people to accept the validity of information and ideas that come from the outside.

Von Hippel further explored the “user innovation” theme in subsequent MIT SMR articles, including “The Age of the Consumer-Innovator,”6 which he coauthored with Susumu Ogawa and Jeroen P.J. de Jong in 2011. In that article, von Hippel, Ogawa, and de Jong reported on new national surveys finding that individual consumers play an important role in both creating and modifying products. What’s more, the authors noted, advances in areas such as computer-aided design tools and 3-D printing mean that “consumers should realize that it is getting progressively easier to design and make what they want for themselves.” Businesses, von Hippel, Ogawa, and de Jong advised, “need to think about how to reorganize their product development systems to efficiently accept and build upon prototypes developed by users.”

Innovation Insight 6

Think of invention as a process of creating new combinations of elements — with results that have a highly skewed distribution.

In a fascinating 2007 article titled “Breakthroughs and the ‘Long Tail’ of Innovation,”7 Lee Fleming explored the dynamics of invention. Defining invention as a “new combination of components, ideas, or processes,” he explained that invention samples show an extremely skewed distribution, with the vast majority of inventions being useless, a few having some value, and only a very few representing breakthroughs.

As a result, Fleming argued that if companies want to achieve breakthroughs they should: (1) make lots of “shots on goal,” since only a few of the inventions they come up with will be breakthroughs; (2) try to increase the average value of each invention; and (3) increase the variability of the ideas they explore — in other words, “take wild shots at a rich target (or preferably a set of rich targets) because the wider range will be more likely to contain scores of maximum values.”

Taking such “wild shots” is one spot where lone inventors come in. Fleming’s research indicated that inventors “working by themselves can be the source of more failures as well as more breakthroughs.” On average, lone inventors are not as creative or as successful as innovative teams — but, paradoxically, the loners are more likely to be the source of breakthroughs because the value of their inventions is so highly variable. One challenge for companies, then, is finding ways to support and manage their lone inventors.

Innovation Insight 7

Understand your options for working with external innovators.

Knowing when and how to open up product development to outsiders is difficult. Which approach is better, working with external innovators organized into collaborative communities (as typified by Linux and other open-source software projects) or tapping into the competitive marketplace for products and services to complement your product? According to Kevin J. Boudreau and Karim R. Lakhani, it depends. In their 2009 article titled “How to Manage Outside Innovation,”8 the authors wrote that the decisions companies make about external innovation should be based on clarity about (1) the type of innovation they need from outside innovators; (2) the motivations of the outside innovators; and (3) the nature of the company’s business model.

The Type of Innovation

Some forms of innovation are simpler to manage than others. When the technology and consumer preferences are clear, Boudreau and Lakhani wrote, companies generally don’t need external innovation: They can develop products internally or hire contractors. However, in cases where some of the design elements are still being determined, opening up the innovation process can lead to significant benefits. Collaborative communities generally work best when dealing with problems that draw on cumulative knowledge that extends beyond what individuals are likely to know. Competitive markets, according to Boudreau and Lakhani, are better suited for problems that would benefit from “broad experimentation across a set of technical approaches or customer groups.”

The Innovators’ Motivations

Just as there are different forms of outside innovation, managers need to recognize that what motivates external innovators varies. Participants in competitive markets tend to be motivated by extrinsic factors such as financial rewards, while collaborative communities involve a greater emphasis on intrinsic rewards, such as intellectual challenge. When evaluating whether to work with collaborative communities or competitive markets, companies should be aware of the different motivators and consider the type of mechanisms needed to align with them.

The Business Model

The third issue managers need to take into consideration when deciding to open their products to external innovation is how that will affect their company’s business model. In determining whether to work with a collaborative community or a competitive market, the authors noted that it’s helpful to ask, “Who sells to whom?” The answer will affect the income streams, the company’s relationship with its customers, and the future role external innovators will play.

Opening your product to external innovation means that it will become a platform, Boudreau and Lakhani explained, and executives must decide which type of platform business model makes the most sense for their business. Companies can either integrate external innovators’ work into their platform, allow external innovators to sell products on top of the platform, or create two-sided markets where external innovators and customers can interact.

Luckily, the authors noted, a company’s innovation strategy needn’t be “cast in stone.” As the needs of the business change, the innovation strategy can change as well. Initially, for example, Apple had a small group of partners producing applications for its iPhone. But within a matter of months, outside developers had developed more than 100 unauthorized applications, prompting Apple to rethink its decision and to establish licensing terms and revenue-sharing arrangements. The lesson, Boudreau and Lakhani wrote, is that “a company needs to tailor its particular approach to the context of its specific business.”

Innovation Insight 8

Create systems and structures that support ongoing innovation.

The most innovative companies know how to do more than simply produce occasional winners. As Scott D. Anthony, Mark W. Johnson, and Joseph V. Sinfield explained in their 2008 article “Institutionalizing Innovation,”9 companies that are seasoned innovators have a set of capabilities that can take them from a plan for growth all the way through execution.

The authors developed their insights into innovation from interviews at more than 40 organizations in an array of industries, a survey, and fieldwork at more than 50 companies. They found that “companies that create blueprints for growth, construct innovation engines, and support the engines with the right systems and mindsets can establish favorable conditions for substantial innovation.”

So, how can companies move in this direction? As a starting point, management needs to develop a “growth blueprint” that articulates what the company “wants to be” — and the specific options it will and won’t consider to reach its objectives.

Another important element, according to Anthony, Johnson, and Sinfield, is determining how the company wants to allocate resources — both money and time — to satisfy its growth objectives. One approach is balancing the innovation portfolio with a mix of improvements to the core business, extensions to it, and growth initiatives in new areas. If a company fails to consciously allocate innovation resources among different types of projects, the authors noted, it will often end up with mostly incremental innovation projects. What’s more, “if the core business runs into trouble, there is an overwhelming temptation to tap resources that the company has allocated to more speculative ventures in order to save the company,” they wrote. “In the short run, this may make perfect sense; in the long run, it can be disastrous.”

Although Anthony, Johnson, and Sinfield highlighted numerous questions that would-be innovators need to confront, they were careful not to be overly prescriptive about the answers. Even within a single company, they argued, managers should be prepared to manage and measure different types of growth opportunities differently.

Companies also need to construct what the authors called “an innovation engine” — which involves structures to screen, develop, and oversee innovative projects. The authors pointed out that there are a number of different innovation structures that companies can use.

Innovation Insight 9

Connect the people in your organization who identify new ideas with those who can commercialize them.

Companies are increasingly trying to bring outside ideas into their innovation processes. To do so effectively requires an understanding of two types of innovation brokers, according to Eoin Whelan, Salvatore Parise, Jasper de Valk, and Rick Aalbers. In their 2011 article “Creating Employee Networks That Deliver Open Innovation,”10 the authors drew on research they had conducted on the diffusion of innovative ideas through personal networks in companies. Whelan, Parise, de Valk, and Aalbers explained the importance of both “idea scouts” and “idea connectors.” Idea scouts excel at identifying novel external ideas, often via the web. But, to effectively implement such ideas, the external focus of idea scouts needs to be complemented by interactions with employees who have extensive networks and influence within the company and a broad knowledge base — a group the authors called idea connectors.

Many R&D leaders pursuing external ideas through open innovation tend to emphasize only the role of idea scouts — which the authors see as a mistake. Companies, they advised, should be thinking about formal mechanisms that bring idea scouts and idea connectors together. “Promising ideas,” the authors wrote, “will not mature into innovative outcomes unless they reach the parts of the employee network that have the expertise and influence to exploit them.”

Innovation Insight 10

Innovation doesn’t have to entail major breakthroughs; it can also involve making new product development faster and cheaper.

According to Peter J. Williamson and Eden Yin, Chinese companies are tackling innovation in a fundamentally different way: Rather than going for major breakthroughs, they aim for faster development cycles. For their 2014 article “Accelerated Innovation: The New Challenge From China,”11 Williamson and Yin studied more than 20 Chinese companies in a variety of industries and found that by breaking the innovation process into small steps and parceling it out to teams, companies were able to complete projects and deliver results faster. These companies, the authors wrote, are “pushing the boundaries of systemization and scale to a whole new level in their efforts to accelerate innovation, leverage the potential of a large pool of competent but often unexceptional technicians and engineers, and reduce costs.”

For example, an outsourcing company serving the pharmaceutical, biopharmaceutical, and medical device industries was able to complete projects two to five times faster than comparable projects using conventional techniques. Similar gains were achieved by Lenovo Group Ltd., which had acquired IBM’s personal computer business. By breaking product designs into modules handled by small teams in parallel, it managed to cut its new product development cycle time in half. Williamson and Yin acknowledged that many of the processes and techniques used by Chinese companies are also being employed by technology companies in places like Silicon Valley. What’s significant, they wrote, is how Chinese companies are bringing “accelerated innovation, with rapid scale-up, low cost, and ‘good enough’ quality” to many different industries.

Innovation Insight 11

Make customer communities your allies.

It’s common for companies to solicit ideas and feedback from their customers and then incorporate what they learn into future products and services. But few have taken customer knowledge as seriously or as far as the Lego Group. In recent years, the Danish toy company, whose multicolored plastic construction toys have been popular with children for decades, has actively explored new and productive ways to engage with the users of its products. As Yun Mi Antorini, Albert M. Muñiz, Jr., and Tormod Askildsen noted, “Through trial and error, Lego has developed a solid understanding of what it takes to build and maintain profitable and beneficial collaborations with users.” These collaborations have led Lego to surprising new areas of growth, the authors wrote in their 2012 article “Collaborating With Customer Communities: Lessons From the Lego Group.”12

Historically, Lego built products for younger children, but in the 1990s, it unveiled a new series of products that appealed to older users. At the same time, the internet facilitated the growth of Lego user groups consisting of adult Lego fans. Lego user groups expanded globally, and innovative products produced by users (for example, a computer-aided design software program for designing Lego models) began appearing. As the authors pointed out, many of the innovations from fans “improved and extended the Lego building system or introduced new ways to use it that dovetailed well with how Lego itself thought of its products.” The company began reaching out to the fan community to solicit marketing ideas or feedback on products in development.

Collaborating with users has it challenges. At times, Lego management found that adult fans lost sight of the fact that the company’s primary end users were children, not adults. In some cases, fans suggested applications that went “beyond the parameters of what the products were designed for.”

From its experience working with its user groups, Lego developed a number of principles for working with customers in product development. One key lesson was the importance of setting expectations up front. After all, users may be eager to contribute their time, but they also have busy lives. (This includes being as clear as possible about the company’s parameters for when projects are expected to begin and end.) Another lesson management learned was that relationships can’t be one way: They need to be not only good for the company but also rewarding for users. “Instead of regarding collaboration as something that needs to be managed exclusively by the company,” the authors wrote, “it is fruitful to think of it as an ongoing dialogue between two allies. Both sides contribute important resources to a common purpose. Frequently, the two sets of resources complement each other and advance the conversation and collaboration.”

Innovation Insight 12

Don’t antagonize your creative people.

In the past, corporate managers often rose through the ranks and thus were very knowledgeable about the activities they supervised. But the rapid changes brought about by technology have created a widening gulf between the expertise of managers and specialized technical employees — something Robert D. Austin and Richard L. Nolan warned that companies aspiring to be technologically innovative will need to address or suffer the consequences. In a 2007 article titled “Bridging the Gap Between Stewards and Creators,”13 they wrote: “Being a good supervisor traditionally meant encouraging sound business practices and introducing changes to those practices as conditions changed. … Now the changes sometimes come from key employees whose work managers don’t completely understand.”

Conflicts between business-oriented managers and technical employees aren’t new. Almost 50 years ago, management guru Peter Drucker highlighted both the importance of knowledge workers and the challenges companies face in managing them. From a study of the development of the internet and interviews with internet pioneers, Austin and Nolan saw how misunderstandings between business-oriented managers (whom the authors called “stewards”) and highly skilled technical employees (whom they termed “creators”) caused delays in the adoption of new technologies. The stewards were most concerned about efficient allocation of resources. Creators, on the other hand, were less concerned about overall efficiency and what was in the business plan and more focused on what they saw as a “higher purpose” and vision.

To a certain extent, Austin and Nolan concluded, disputes between stewards and creators are an inevitable — even useful — part of the innovation process. The challenge, they explained, is learning how to manage the tension, for which they put forth a set of guidelines. One of their guidelines for managers is to avoid antagonizing creators, even if it means putting up with someone who is difficult to manage; an effort to get rid of one creator could snowball into losing two or three, leaving the company short on key creative talent. As Austin and Nolan wrote, “Putting up with a certain amount of maddening behavior by creators may be a price worth paying to keep great talent.” Another recommendation is to cultivate people who can speak the language of both creators and stewards — they may be helpful in mediating internal conflicts.

“The challenges in managing someone who never wants to do the same thing twice and who keeps going off on tangents are substantial and quite different from the more traditional challenges” managers face, the authors observed. But managers who don’t learn how to manage creators run the risk of missing big opportunities, and they “won’t have much fun in the process, either.”



Bruce Posner is a senior editor at MIT Sloan Management Review. Martha E. Mangelsdorf is the editorial director of MIT Sloan Management Review.

https://www.anothertrail.com/archives/74448/feed 0
Plexxi HyperConvergence Test https://www.anothertrail.com/archives/16204 https://www.anothertrail.com/archives/16204#respond Sun, 13 Aug 2017 08:51:00 +0000 http://www.anothertrail.com/?p=16204 This ESG Lab Review documents hands-on testing of Plexxi HCN for Hyperconverged Infrastructure (HCI) with a focus on ease of use, performance, resiliency, and best practices for configuration in HCI environments.

Choose Easy Or Hard - Difficulty Levels What it all means?: you get predictable performance, anytime, in any condition, uner any workload. Guaranteed. In one DC, across DCs.


https://www.anothertrail.com/archives/16204/feed 0
The need for a Predictable network in the DataCentre https://www.anothertrail.com/archives/16209 https://www.anothertrail.com/archives/16209#respond Mon, 19 Jun 2017 05:26:00 +0000 http://www.anothertrail.com/?p=16209

What is HyperConvergence

Legacy data centers originally designed to support conventional client-server applications can’t meet the increased agility, scalability and price-performance requirements of today’s virtualized IT environments. Conventional data centers composed of independent compute, storage and networking platforms are costly to operate and scale, and difficult to administer and automate.

Most legacy data centers are made up of distinct servers and storage arrays with separate Ethernet LANs for data traffic and storage area networks (SANs) for storage traffic. Each technology platform (servers, storage arrays, L2 switches, SAN switches) consumes power, cooling and rack space, and supports a unique management interface and low-level APIs. Rolling out a new application is a manually intensive, error- prone process involving a number of different people, devices and management systems. Turning up new IT services can take days or weeks and involve multiple operations teams. Troubleshooting problems or orchestrating services can be just as difficult.

Many IT organizations are looking to hyperconverged integrated systems1 (HCIS) to reduce infrastructure cost and complexity. In a Gartner survey, 74% of respondents indicated they are using, piloting or actively researching HCIS solutions. Next-generation HCIS solutions from vendors like Nutanix and SimpliVity pack compute and storage resources into compact x86 building blocks that are fully virtualized and uniformly administered. Hyperconverged systems contain CAPEX by collapsing compute and storage silos and eliminating SANs. And they contain OPEX by reducing IT sprawl and lowering recurring power, cooling, rack space and administrative expenses. By consolidating and unifying the compute and storage domains HCIS solutions can reduce TCO, accelerate time-to-value and simplify operations. But many enterprises fail to consider the networking implications of HCIS. Current data center networking constraints can hinder IT service agility, impair the performance of contemporary applications and hamper HCIS initiatives.

Re-architecting Data Center Networks for HCIS Implementations

Hyperconverged systems consolidate diverse applications, workloads and traffic types onto common infrastructure, introducing network engineering challenges for IT planners. Conventional data center networks designed to support siloed IT environments aren’t well suited for carrying diverse HCIS traffic. Most are simply overprovisioned to support peak traffic demands—an inefficient, application- agnostic approach that squanders bandwidth and budget. And because all workloads are treated equally, a data-intensive or bursty application can monopolize network capacity, impairing the performance of other applications (the so-called noisy neighbor problem).

As Gartner (1)  points out “Mixing user access, node-to-node application traffic, VM mobility, storage access and back-end storage traffic on a single network can lead to unpredictable performance, availability and data integrity.


When implementing HCIS solutions, IT planners must make a reset on their old practices and re-architect data center networks to ensure adequate performance and service quality for all applications.

(1) Gartner’s “Leverage Networking to Ensure Your Hyperconverged Integrated Systems Can Support Demanding Workloads”

(2) This article is inspired from a joint paper Gartner/Plexxi

https://www.anothertrail.com/archives/16209/feed 0
The financial industry contained an average of 52 open source vulnerabilities per application. London we have a problem! https://www.anothertrail.com/archives/16213 https://www.anothertrail.com/archives/16213#respond Mon, 08 May 2017 08:09:00 +0000 http://www.anothertrail.com/?p=16213 For many years, DTmag has been reporting open source security issues, and two studies within the past couple weeks demonstrate there is a problem: Last week, this site reported on a study conducted by German researchers that linked open source software vulnerabilities to developers copying source code from flawed online tutorials and pasting it into open source applications.

The financial industry contained an average of 52 open source vulnerabilities per application, while 60 percent of the applications contained high-risk vulnerabilities, the company said. It added: “The retail and e-commerce industry had the highest proportion of applications with high-risk open source vulnerabilities, with 83 percent of audited applications containing high-risk vulnerabilities.”


Our view?: as open-source is a very valuable approach, and vulnerabilities will keep existing; better have a new strategy for protecting your information/data. It’s time to have a real visibility of “intents” of attackers, this is the key.

This is why we’re embracing technologies such as http://www.empownetworks.com

source: https://adtmag.com/articles/2017/05/01/black-duck-audits.aspx

https://www.anothertrail.com/archives/16213/feed 0
Will we rebuild 2 Tier Architectures for the Cloud to deal with Latency? https://www.anothertrail.com/archives/16218 https://www.anothertrail.com/archives/16218#respond Sun, 16 Apr 2017 16:13:00 +0000 http://www.anothertrail.com/?p=16218 This article highlights an important question that will pop up soon. Maybe we’ll re-invent what came 30 years ago.. a 2 tier architecture w/ front-end and back-end servers? The Cloud being the Back-end.

IT is a wheel..from Mainframe to mini, from mini to PCs and back-end, two tier architectures, distributed systems, cloud..and now?

source: http://formtek.com/blog/edge-computing-cloud-latency-cant-support-real-time-iot-and-ai-apps/

Edge Computing: Cloud Latency Can’t Support Real-Time IoT and AI Apps

By Dick Weisinger

Is the Cloud the ultimate solution?  Many of the benefits of the cloud can be alluring. Security has long been a pain point, but cloud security is increasingly less of an issue, and security has been steadily improving.

One issue remaining issue with the cloud that won’t go away anytime soon is latency.  Cloud apps are slow compared to apps that run on local machines.  Network latency, the time it takes data to travel from devices to the datacenter and back, is a problem for any application that needs immediate feedback of information.

Peter Levine, general partner of Andreessen Horowitz, told the Wall Street Journal that “I have this theory that cloud computing goes away in the not-too-distant future. I believe there is now a shift, a return to the edge where computing gets done much more at the edge than in the cloud. The Internet of Everything, specifically if you think about self-driving cars, is a great example of this. A self-driving car is a data center on wheels. And it has 200-plus central processing units. It’s got to do all its computation at the endpoint and only pass back to the cloud, if it’s connected at all, important bits of curated information.”

Deepu Talla, VP and General Manager of Mobile at Nvidia, said that “by 2020, there will be 1 billion cameras in the world doing public safety and streaming data. There’s not enough upstream bandwidth available to send all this to the cloud. Latency becomes an issue in robotics and self-driving cars, applications in which decisions have to be made with lightning speed. Privacy, of course, is easier to protect when data isn’t moving around. And availability of the cloud is an issue in many parts of the world where communications are limited. We will see AI transferring to the edge.”

Thomas Bittman, analyst at Gartner, wrote that “there’s a sharp left turn coming ahead, where we need to expand our thinking beyond centralization and cloud, and toward location and distributed processing for low-latency and real-time processing. Customer experience won’t simply be defined by a web site experience. The cloud will have its role, but the edge is coming, and it’s going to be big.”

https://www.anothertrail.com/archives/16218/feed 0
IT Infrastructure should be designed to understand the “intent”. Only the “intent”? Not just!, add real-time! https://www.anothertrail.com/archives/16222 https://www.anothertrail.com/archives/16222#respond Sun, 02 Apr 2017 20:43:00 +0000 http://www.anothertrail.com/?p=16222

For Networking, understanding what the Application intends to require in resources

For Security, what the hacker wants to do

But not yesterday, now!

Sharp article from MIT Sloan Mngt review: https://goo.gl/jgTpgn  (extract follows)IMG_0982

The future of IT includes those keywords: “intent”, “abstraction”, “real-time” and indeed Applications. The rest is technology?

https://www.anothertrail.com/archives/16222/feed 0