👐    metier   👐    design: bpm    sdlc    bianl    sense    data    meta    math    👐    devops: bpm    sdlc    bianl    sense    data    meta    math 👐
👐    Intro     innxstbl     add-aim    add-emoi    wall-cnfs     post_vln    👐    top bottom   👐

Conflict of interests (design bpm)


Four quadrants: Innovation X stable Operations, value - complexity

Clockwise, CounterClockwise

Poldermolen_openluchtmuseum. A cyle goes around.

A windwill goes counterclockwise. For convenience the proces life cycle is clockwise

🔰 the most logical begin anchor.


Contents

Reference Topic Squad
Intro Clockwise, CounterClockwise 01.01
innxstbl Conflict of interests, Innovation X Stable operations 02.01
Issues to solve at Analtics life cycle 02.02
add-aim Placing organsiational lines into innovation X operations 03.01
add-emoi Adding emotions into quadrant 04.01
wall-cnfs Communication: request - delivery 🚧 Expectations 05.01
Communication: request - delivery 🚧 Disruptions 05.02
post_vln Evaluating, What others post 06.01

Progress


Conflict of interests, Innovation X Stable operations

Innovation X Stable operations The dilemma is what is hanving the priority.
Starting with an innovation and than making that robust and stable or
Making the running processes stable and than innovate.

That question is of getting anserwers to business value and complexity - simplicity.
A startup doesn´t need to get answer on that.


labeling the quadrant:
  1. Doing things as used to be (push)
    rigid but: predictable repeatable reliable.
  2. Ideal combination of new innovations and being trustworthy.
  3. Adhoc, nothing as should be operational or legal
    but maybe having the necesssary new opportunities.
  4. Innovation, changing the business by doing things different. (pull)
Obvious is "doing things different" is conflicting with "doing things as usual".

Issues solving coöperation innovation X operation

The challlenge to solve the conflict is an mission impossible. The issues are well known for a very long time. New technologies like moving into the cloud -AAS delivering by external parties will not solve it.

SukumarNayak (2015) did publice a nice presentation on all kind of organizational issues. Showing a figure:
confusion developement operations
He refers to what-is-devops.
Don´t expect the misalignment will be solved by placing the people for the different roles in a room. With cloud approaches you are placing people outside the organization.

Business-IT alignment is a process in which a business organization uses information technology (IT) to achieve business objectives - typically improved financial performance or marketplace competitiveness. Some definitions focus more on outcomes (the ability of IT to produce business value) than means (the harmony between IT and business decision-makers within the organizations). (wikipedia)

Placing organsiational lines into innovation X operations

Just a hierachical pyramid like many others. Strategy being on the top, Tactics in the middle, Development & Operations at the bottom. The data symbol in the middle is ised in another page. It has no meaning, no place, at this paragraph.

The business service request is at the right side (developping, changing business), the service delivery at the left (operations, supply chain). The circle is following this logical order. The figure:
AIM pyramid into a cycle
When turning the pyramid 45 degrees clockwise it will fit into the "Innovations X Stable operations" quadrant. The departments for the best fit location according the quadrant descriptions.

The figure transforms into:
Innovation X stable operations add hierarchy
In the middle of the quadrant there is the "wall of confusion".

Adding emotions into the inno quadrant

Working in organizations is managing humans and managing technology.
pyramid work top pyramid work reverse top Normal thinking: top-down human management, a pyramid. (left)
Effective technical staff supports as many as possible,a reversed pyramid. (right)
The dependencies on the top or the bottom are both single point of failures.

The business ICT proces is involving many types of specialists: Innovation X stable operations add hierarchy- emotions

Putting in some nice figures into those three quadrants.
The quadrant III nobody wants to be at, a feeling of wild environment.
Maybe the quadrant III is having the big hidden opportunities to be found, in that case anohter more warm feeling is appropiate. The picture I will use is showing a friendly happy daily trip. What is not there is an easy way to go ashore.


What more is to say ......:
More links associated - entry/exit
Is used at:
👓 threats for data & tools Proces Life Cycle.
Details to be found at:
..

Communication: request - delivery 🚧 Expectations


Note the counterclockwise rmovements by the animation for changing technical impediments. (data tools)
There are a limited number of ways to get the requests correctly done.

Communication: request - delivery 🚧 Disruptions


Note the counterclockwise rmovements by the animation for changing technical impediments. (data tools)
There much more ways to do it incorrect as to do it correct.

Evaluating, What others post

When this "quadrant of interest conflict" is understandable, the following ones also are making sense:
Imrich data to data-science
Xomnia Imrich

I to IV, Data delivery by =DW support= falls into "business as usual".

four quadrants - data modelling
data quadrants

I to IV, Data delivery by =DW support= falls into "business as usual".


The unsolved question is how to achieve innovation, counterclockwise pull, when the other force is clockwise push. The magic that an innovative stable proces would be created out of nothing, makes no sense.
A holostic strategy view: Proces Life Cycle.

🔰 the most logical begin anchor.



👐    Intro     innxstbl     add-aim    add-emoi    wall-cnfs     post_vln    👐    top bottom   👐
👐    metier   👐    design: bpm    sdlc    bianl    sense    data    meta    math    👐    devops: bpm    sdlc    bianl    sense    data    meta    math 👐

© 2012,2019 J.A.Karman