Visar inlägg med etikett digitalization. Visa alla inlägg
Visar inlägg med etikett digitalization. Visa alla inlägg

söndag 23 maj 2021

Practical steps to efficient automation


Everyone in the vicinity of IT systems, application and software knows that the promise of the potential benefits looks absolutely irresistible from a distance, or in a sales pitch, but when it comes down to the nitty gritty details of using the end result, customer satisfaction is not always on par with the initial impressions.

Automation, like any efficiency improvement straddling organization, human behavior and technology, runs a similar risk of disappointment – hence, if our aim is to overdeliver on customer expectations, we have a number of practical steps to follow based on our previous experience and, ideally a methodology framework.

To emphasize the difference, and additional potential pitfalls, whether we were discussing replacing an existing integration between two systems, or establishing a new integration for data transfer, the success criteria are quite obvious, and practically binary;
  • Does the data end up where it should?
  • Is it the right data?
  • Is it on time?
  • Is the solution resilient enough to handle deviations in content, system availability etc?

...together with the ‘standard’ expectations of the overall delivery being on time, on budget and managed professionally (communication, planning, pricing etc).  When it comes to improving  efficiency that affects on organization, human behavior and technology combined, the challenge is practically exponentially more complex.  So, what makes the effort to automate efficient, and how can these steps be achieved from a practical perspective?  Let’s break it down into the challenging areas mentioned above; organization, human behavior and technology.

Organization

Sometimes, we can ‘get away’ with working within a limited workflow, or a couple of isolated processes handled within the same team, the same department. But in most cases, real efficiency drivers are discovered in our cross-functions, between roles, departments or applications (with different owners). This is a common source of grief and potential project pitfalls; when there are shared responsibilities, unclear ownership or unknown escalation paths, the projects run a serious risk of falling behind schedule or delivering a solution which doesn’t fit real-world requirements.

The solution is to engage with all relevant stakeholders and individuals, regardless of formal area of responsibility, required to align towards the common goal, and anchor the solution buy-in with them. A practice usually recommended, is to form an Automation Center of Excellence as a forum to handle cross-area issues, promote the benefits of automation, and communicate with all parties within the organization to make sure everyone is informed, onboard, and aligned.

Human behavior  

On the smaller scale, individual human behavior can and should not be underestimated as a risk factor.

Even though most of us have a generally optimistic outlook on new ideas, on the subconscious level we’re often leaning towards resisting new ways of doing things, changing “the way it has always been” and bringing in practices that are “not invented here”. Although mentioned as a risk, it can easily be converted into a great asset and enabler, tying into the Automation Center of Excellence concept. The practical step to this stage is to untap the hidden potential and wisdom ‘hidden’ within the experience and knowledge of each co-worker.  Make sure everyone gets the opportunity to engage, to participate, contribute to the discussion on the solution design, ideally through process discovery workshops – where a common way of working and real gems of efficiency drivers can be identified. 

This way, a better sense of understanding and ownership can be established in the teams who – in the end – will actually own and benefit from the new functionality.  As automation can sometimes be portrayed as dehumanizing or replacing jobs rather than as an enabler to allow for proactive troubleshooting, problem solving and creative innovation, this approach will also defuse such views and contribute to a positive reception when the time for change management comes.

Technology

Technology is great at doing what we ‘tell’ it.  The problem is, if we don’t think through the instructions well enough, the result can be a disaster.  Therefore, small steps, and taking those small steps in the right order, is a success factor. The process discovery activity mentioned earlier, can provide you with vital input on which workflow, out of several candidates, to support with automation, and – crucially – how to design the automation without producing a ‘carbon-copy’ process of the human-based labor-intensive way of working. Technology and automation require an approach with the best from both worlds, to make the most out of its potential. 

Once the scope is established, the implementation should follow along similar lines, operate with quick iterations, be agile and test and release often to make sure the end user get a chance to provide feedback and input.  Don’t forget - The gains achieved through the joint effort is a team win – celebrate the victories accordingly!

To summarize:

  • Engage across the organization, initiate an Automation Center of Excellence
  • Involve and enthuse, frame and emphasize the investment in improvements and benefits to the individual roles.  Promote participation and contribution.
  • Start small – keep it simple, and build on the positive momentum of continuous gains
  • Work agile, test and release often – and highlight the concrete efficiency improvements with each step.  A little bit of evangelizing internally goes a long way to grow enthusiasm and interest.
  • The achievements are a team effort – celebrate the results and victories as a team!

This is the second of a four-part blog post series about intelligent automation, using technology in a smart way to get the most out of the time, energy and overall investment each organization is faced with to improve Customer offering, quality and overall market competitiveness.

Are you looking for ways to leverage technology to benefit your business and outsmart the competition?  Get in touch - every step forward starts with a constructive and thorough discussion!

 

måndag 31 oktober 2016

Peace for Our Time



A phrase spoken on 30 September 1938 by
British Prime MinisterNeville Chamberlain in
his speech concerning the Munich Agreement and
the Anglo-German Declaration
An epic age-old battle is raging across the centuries, between good and evil, Microsoft/Windows users and Apple/OS X users, law enforcement and criminals, Java developers and .Net developers, blackhats and whitehats, emacs vs vi users, heavy metal fans and synth fans, orcs and humans, and so on and so forth ..

Fanatics on each side are entrenched in their legacy experience and convictions, preferences, tastes - making it impossible to see the other side of the argument, because it's of course just wrong.

In the project management context, this typically translates into choosing sides between methodology approach - waterfall, or agile - with the agile approach having lured throngs of followers to abandon the traditional waterfall methodologies for heretical beliefs in happier colleagues, Customers and outcomes working with Epics, Stories, Sprints and Stand-ups .. and securing Customer (or key stakeholder) involvement in reprioritization of requirements and scope.

Don't get me wrong - I sincerely believe that each method has its merits, it's just that the waterfall approach was better suited to the main bulk of projects I was involved in during my formative career years, thus making other approaches less comfortable.

I think most of you are familiar with the principles of the waterfall model, and perhaps even some of its origins going back to the very early days of software development, later to be adopted and refined by the US Department of Defense.

There's a plethora of sources online going into all kinds of variants, descriptions of the method etc - so this won't be a detailed walkthrough recapping such content.  Let's just agree that it typically outlines various stages in a sequential fashion where the completion of the preceding stages are prerequisites to starting the latter.

Example –
Preliminary Design, Detailed Design, Coding and Unit Testing, Integration, and Testing
 .. or ..
Requirements capture, Analysis, Design, Coding, Testing and Operations

With roots in the manufacturing and construction industries, the blueprint must be established before the assembly can begin etc.

A contrarian approach to the waterfall model, would be Scrum, considered to be one of the most successfully proclaimed and adopted agile methods.  It's iterative, incremental, and actually encourages the scope and prioritizations to change with time as the project moves along.  Quoting Wikipedia -"A key principle of Scrum is its recognition that during product development, the customers can change their minds about what they want and need .." This is quite different from the waterfall approach as e.g. changes to solution design discovered during testing would require replanning, re-"tooling", and reimplementation (you can tell already that it's costly) not to mention that it may trigger other changes due to dependencies in the solution.

We'll revisit the notion of actually involving the Customer continuously in the decision making- and planning process in a later post, but make no mistake - this is a key success factor regardless of methodology, it's more a matter of timing, setting expectations and communicating correctly.

With the peacekeeper hat on, one is obliged to say that both methods carry strengths, merit as well as weaknesses - so which one is the wiser choice?  None? - Both!

The "Pragmatic approach" in my view is to base the choice of method on the context at hand, and there's a simple perspective which can be applied to do it - "Goals and Methods matrix".  With roots in an academic paper from 1993 where Turner and Cochrane state that traditional definitions view a project as ..

- “a complex sequence of activities to deliver clearly defined objectives  ...  and the goals and the method of achieving them are well understood at the start of a project, or at least at the start of its execution stage”
(Turner & Cochrane, 1993: 93).

.. - and propose an alternative view; that a project should be categorized by the extent to which the goals are more or less clearly defined, together with the extent the method to achieve the identified outcomes (scope, deliverables) is known.
 

With such a categorization, it becomes a little easier to take a step out of the comfort zone and acknowledge that the favorite method may not be the tool best suited to the task.  Just imagine taking an agile approach to building a car for each new vehicle ordered (low production rate ..) or applying the waterfall model to exploratory research (let he who hasn't exceeded his budget cast the first stone ..)

Sometimes, even a mix between the two (usually described along the lines of a v-shaped spiral) might be the most productive strategy even though it may send chills down the spine of puritans.

At Enfo, we support our Customers with a similar approach when it comes to digitalization initiatives and capturing the value of innovation, which often take the shape of a technical solution implementation project in combination with an organizational change at the same time.  Changing the way you do business and interface with Your Customer can rarely be accomplished within the same organizational setup as the vehicle taking you to where you are today.  Hence the need to address both areas, which is likely to require slightly different choice of method.

The industry trend of viewing and categorizing investments through the "bi-modal lense" (fast/slow, marathon-runners – sprinters, ninja-samurai, innovation/operations) is also enabled through this method approach.

It's not a question of abandoning your faith, making a deal with Hitler, selling your soul to the Devil, or giving up on your principles - but - at the start of your next assignment, try to map out where your organization, project and goals fit in on the matrix and keep an open mind on how to approach the choice of project method thereafter.  Perhaps it’ll take us a step closer to peace for our time!
 
By Fredric Travaglia, Business Development Consultant @ Enfo

https://en.wikipedia.org/wiki/Waterfall_model
https://en.wikipedia.org/wiki/Scrum_(software_development)
Turner, J.R. and Cochrane, R.A. (1993) “Goals-and-methods matrix: coping with projects ill-defined goals and/or methods of achieving them”, International Journal of Project Management, vol.11, no. 2.
http://www.enfo.se/
http://www.enfo.se/Den-Digitala-Dimensionen
http://www.travaglia.se/2016/06/id-like-two-scoops-of-change-please.html
http://www.travaglia.se/2015/10/who-is-your-customer.html
http://www.travaglia.se/2015/11/let-trend-be-your-friend_24.html
http://www.gartner.com/it-glossary/bimodal/
http://www.thedigitaldimension.com/Posts/Video-Logs/2016/Innovation/Create-and-capture-value-in-the-digital-dimension

måndag 17 oktober 2016

Avoiding the Great Extinction

Regardless of if you are in the manufacturing business, or if you operate in the service industry – competition is a constant, and the pursuit of alternative solutions and suppliers is never ending.  How can you avoid going the way of the Dodo, and stay competitive in business?

Looking at recent history, there are plenty of evident changes where lessons can be learned, and insights into what the differentiating factors may be to either avoid a similar fate, or benefit from the rolling trends and changes occurring.

Manufacturing has continued to migrate and become outsourced, off-shored, over the past 25 years
From textiles, to heavy manufacturing and high tech / electronics, the exodus is moving higher and higher in the value chain.

East and South Asia offer superior labor arbitrage unrivalled on local western markets when global free trade facilitates the transfer of manufactured goods and eliminates trade barriers.
In the pursuit of faster, better, cheaper (and redundant manufacturing capacity where import tariffs still apply) it's a race to the bottom on cost, when outputs and tooling (quality) are standardized

The latest example from a Nordic perspective is the telecom industry where practically all manufacturing is shut down (Nokia, Ericsson) regardless if it is handsets or network equipment.

Design, intellectual property and service (consumer, Customer) relationship resides with local market - together with higher steps in the value chain.  "Designed in Palo Alto, CA - Made in China", is the new black.

The IT and service industry is the current big wave leveraging commoditized outputs and economies of scale.  Callcenters, Customer services facilities, IT Services are under immense price pressure - HCL, Tata/TCS, Tech Mahindra .. the list of huge resource pools of standardized competencies is growing and becoming more complex and sophisticated by the hour.  The argument that it's only applicable for non-creative work is disappearing as rapidly as the budgets allocated to local suppliers.

 As if that wasn't enough to assimilate in existing business models, the hardware and capacity services is undergoing a silent revolution where Amazon (Web Services), Microsoft (Azure), IBM (Softlayer) are offering dollars' worth of hardware capacity on the dime through their massive datacenter investments (Microsoft, Google, Apple, Amazon), combined with extreme flexibility and service expansion "on the dial".  The incentive to invest in in-house server capacity and capabilities is rapidly diminishing, together with related management services, and local hosting services.

What countermeasures are available to local players on the market - what can you offer, what do you need to be and do to become indispensable, essential, to your Customers value creation and offering to their Customers?

To summarize –
1. Package and bundle competencies
2. Offer domain and industry expertise
3. Offer fixed price solutions – minimizing risk
4. Strive for partnership rather than vendor-supplier status
5. Offer Excellent Service

1. Packaging and service bundling of multi-discipline competencies
Like any manufacturing operation will prove, the more complex the output - the better the margin, as more value is packaged and provided to the Customer.  Lumber in a stack and nails in a box yield little margin, but prefab housing is good business.  It's the combination of basic skills, tooling, complex skills and experience that raises the yield in the value chain.

2. Domain and industry offering
Regardless of your industry and business, that is typically what you know best.  If you can get a Customer who's in the same business, you can guide them past all the paths they shouldn't be going down, based on your own experience.

The problem is that the players in your industry and business are most likely competition, rather than potential Customers – but most Customers are looking for something in addition to the bread and butter content of the core offering you provide together with the competition in your field.  Differentiating and leveraging the core offering with domain and industry specific offerings, providing solutions and value rather than just the nuts and bolts for DIY (the assembled table and a takeaway order for dinner rather than the flat pack assembly and directions to the grocery store)

3. Fixed price models
Coupled with taking out risk from the equation for the Customer, and thus offering fixed price for a delimited outcome – suppliers start to become enablers and business partners rather than just vendors.

4. Partnerships - ..
.. with the Customers - becoming part of their operation, winning and losing together, sharing risks and rewards.  Proactively engage and collaborate with their strategic business initiatives.
.. with frontline players who can complement your offerings with domain and industry specific expertise.

Mixing these factors, interfaces and values provided to the Customer – you become indispensable, a critical key component and success factor – to your Customer.

This makes your business incomparable to standardized, commoditized offerings, measured and priced in $/unit (Gb, hour, FTE ..) - making the wave of outsourcing, offshoring and detrimental price-race to the bottom irrelevant.

5. Offer Excellent Service
Realize, accept and act on the fact that the offering, the value, the services and the Customer relationships are only as good as yesterdays’ delivery, and that your competition is constantly looking to get an edge over what we already offer - so should you!

Piece of cake, right – you’re already doing this, or planning to do it?  Perhaps not, but more importantly – there has never been a more advantageous time to endeavor to do it, than now!

The opportunities and capabilities to collaborate closely, share information on Customer behavior, real-time forecasts, etc are unprecedented given the information technology tooling and platforms available.

The Digital Customer Experience, is yet another step towards building that close-knit, indispensable position in relation to your Customer, and obtaining information crucial to creating partnerships with co-suppliers of expertise and complementary value.  Take a step forward to create and capture value in the Digital Dimension!

By Fredric Travaglia, Business Development Consultant @ Enfo

http://www.reuters.com/article/us-sweden-ericsson-idUSKCN11S0G9
https://www.engadget.com/2012/01/22/why-apples-products-are-designed-in-california-but-assembled/
http://www.winbeta.org/news/microsoft-spend-15-billion-building-data-centers-year
http://datacenterfrontier.com/cloud-wars-intensify-google-adds-more-data-centers/
http://www.datacenterknowledge.com/archives/2015/02/23/apple-spend-2b-two-massive-european-data-centers/
http://www.seattletimes.com/business/technology/amazon-microsoft-invest-billions-as-computing-shifts-to-cloud/
http://www.thedigitaldimension.com/Posts/Video-Logs/2016/Innovation/Create-and-capture-value-in-the-digital-dimension
http://www.thedigitaldimension.com/