From fixed to relative performance contracts
and towards simple, ethical and empowering ways
of dealing with value creation
Sydney, 15.10.2015
Cubewise Performance Management Leadership Forum
@NielsPflaeging
Why management is quackery. Keynote by Niels Pflaeging at HFU Business School...Niels Pflaeging
Why management is quackery. And what leadership for the 21st century must really look like - keynote at HFU Business School, Villingen-Schwenningen, December 2013
Startup Exit Strategy: Why, when, and how to sell your technology startup to an acquirer. Discusses Lean Startup + Early Exit model. Tips for early stage M&A, exit planning, and doing the deal.
Why management is quackery. Keynote by Niels Pflaeging at HFU Business School...Niels Pflaeging
Why management is quackery. And what leadership for the 21st century must really look like - keynote at HFU Business School, Villingen-Schwenningen, December 2013
Startup Exit Strategy: Why, when, and how to sell your technology startup to an acquirer. Discusses Lean Startup + Early Exit model. Tips for early stage M&A, exit planning, and doing the deal.
Notes are not enough! Why relying on your notes will lead you down the garden...Ash Donaldson
You take great notes, right? Have you ever compared them to a transcript?
It’s amazing how much of the important stuff we miss as we take the time to interpret what someone says, formulate what we’re going to write, then go through the physical act of writing before switching back into listening again.
In this presentation we’ll walk through the model of communication, exploring the limitations of perception, cognition, attention and memory. By the end I hope you’ll appreciate why your notes are not enough.
Presented at Design Research 2017, Sydney
Organisationen müssen heutzutage die Fähigkeit besitzen, sich an ein veränderliches Umfeld anzupassen. Selbes gilt auch für das Management und die Organisation von Projekten.
Agile Prinzipien und Frameworks zeigen die Richtung klar auf. Auch Projekte und Projektmanagement müssen in diesem Sinne "dynamikrobust" gestaltet werden, um wertvolle Ergebnisse zu liefern.
Notes are not enough! Why relying on your notes will lead you down the garden...Ash Donaldson
You take great notes, right? Have you ever compared them to a transcript?
It’s amazing how much of the important stuff we miss as we take the time to interpret what someone says, formulate what we’re going to write, then go through the physical act of writing before switching back into listening again.
In this presentation we’ll walk through the model of communication, exploring the limitations of perception, cognition, attention and memory. By the end I hope you’ll appreciate why your notes are not enough.
Presented at Design Research 2017, Sydney
Organisationen müssen heutzutage die Fähigkeit besitzen, sich an ein veränderliches Umfeld anzupassen. Selbes gilt auch für das Management und die Organisation von Projekten.
Agile Prinzipien und Frameworks zeigen die Richtung klar auf. Auch Projekte und Projektmanagement müssen in diesem Sinne "dynamikrobust" gestaltet werden, um wertvolle Ergebnisse zu liefern.
The Perfectionist’s Bathroom
What does it take to get a User Focused Design process introduced into a large Australian Health Insurer – some pitfalls, some observations and just a little bit about bathroom design.
Presented at Agile Australia 2016.
My team has spent 5 years figuring out how best to follow Agile methodologies and maximise the opportunities we have through design. This journey has had many ups and downs. Along the way we have tried many new methods, evaluated, twisted and turned to get where we are today. My guess (and hope) is that there will be many more twists and turns in the future.
One thing I have learned is that the ability to communicate the value of what we do and the way we do it is paramount to the continuous improvement in our practices.
In this presentation I will step through 5 diagrams I frequently draw on whiteboards that not merely explain the way we work as designers but help others to understand why we design. These will be our “designer mindset”.
Take away clear visualisations around experience, design thinking, process, expertise, collaboration and the effectiveness of design. Recreate and iterate these visualisations to enhance your own designer’s mindset.
What's next for Interaction Design? The future is now! Robots, autonomous machines, AI, IoT, sensors, data, networks and intelligent systems. Here's a whirlwind review of some of the more transformational aspects of Interaction Design in the coming years, as portrayed by a select few of the fantastic speakers at interaction16 in Helsinki earlier this month. #IXDASYD #IXD16
Potholes on the Journey to Design TransparencyJake Causby
Design transparency is the most effective way to communicate with your stakeholders and give them insight into your design process. This presentation focuses on cultural changes, ways to share, and how to collaborate with stakeholders. To hear the audio, visit http://www.uxaustralia.com.au/uxaustralia-2012/potholes-on-the-journey-to-design-transparency
The gap between physical and digital has blurred: we use Wiis to get in shape, computers to order a pizza, or our smartphone’s GPS to find hot dates. People want to interact with products and services when they want to and how they want to – and that’s not always on the web.
The future of design is everywhere the customer touches our product or service - digital or physical. User experience practitioners must move beyond the screen to designing a holistic customer experience that is seamless across channels and devices.
Ten minute presentation that attempts to distill a handful of IxD14 talks down into 30 second snippets then questions what it means when people say design is part art and part science. Special thanks to the legends: Bernard Lahousse, Christina Wodtke, Klaus Krippendorff, Stephanie Akkaoui Hughes, Giles Colborne, Dan Rosenberg, Irene Au, Peter Bil’ak, Antonio de Pasquale, Jason Mesut and Dave Malouf.
A Million Little Ideas – Design Panel
Farbs, Terry Paton, John Lycette, Ash Donaldson. Chair: Simon Joslin
Everyone has an idea for a game (or a million of them), but how do you identify which ones to pursue and which ones to leave by the wayside. And how do you evolve that idea into something workable, incorporating everyone else’s ideas along the way. This session looks at the pursuit of that one brilliant, shining, life changing moment – and the work that goes into making it real.
http://www.freeplay.net.au/2010-session-details/
Design for Complexity. Webinar with Niels Pflaeging organized by On The MarkNiels Pflaeging
Illustrations from the book Organize for Complexity by Niels Pflaeging, available under http://www.amazon.com/Organize-Complexity-Build-High-Performance-Organization/dp/0991537602
This slide deck dives a bit in history to understand where IT comes from, where we are now and why we are there and what our options are. It starts with exploring the paradigms of the markets companies live in, travels through matching organizational approaches and finally looks at the history and current state of IT.
Based on that and after a quick look at Conway's law the market paradigms and organizational approaches are evaluated with respect to the drivers they imply on IT in general and architecture particularly.
And after all that foreplay (which is necessary to really understand where we are and what the forces are) several architectural styles and technologies are located on the scale that the market paradigms and organizational approaches span. This way sort of an "architectural fitness detector" is provided which helps to make architectural choices based on needs instead of hypes or habits (which are way to often the choice drivers).
The slide deck then finishes up with a few mismatches that are seen quite often in reality and it can be seen how the distance between architectural choices on the presented scale can be used to quickly determine potential mismatches.
As always the voice track is missing but I hope that the slides are still of some help for you.
"Why DevOps is not enough" by Uwe Friedrichsen
The DevOps movement is gaining momentum - which is good. But still DevOps often is seen way to small. DevOps is not only some more collaboration between Development and Operations. It is the implementation driver for a massive change in IT - and it is not enough in itself. In this session we will examine the drivers and goals behind DevOps, why we need the change, how DevOps affects the whole IT and what else is needed to really "become DevOps". We will develop an "DevOps ecosystem" and draw the missing lines between several important concepts that all feed into the actual goals behind DevOps.
DevOps is not enough - Embedding DevOps in a broader contextUwe Friedrichsen
As the subtitle says, this talk tries to embed DevOps in a broader context. Therefore first briefly is sketched, how the state of IT is perceived by many people in IT. Additionally, DevOps is briefly defined by explaining the three ways as they were described in the book "The Phoenix Project".
After this short introduction the claim of the title is picked up: "Why is DevOps not enough?". In order to explain this claim, the history of economic markets and of IT are briefly explained. The bottomline is that almost all markets supported by IT have drastically changed in the years since IT became relevant for companies. Additionally, IT itself has changed dramatically in this period of time. Therefore, most of the common knowledge and best practices, we stick to in IT became counter-productive meanwhile because they solve a completely different problem, i.e., the problems of the times when the markets and IT itself were totally different.
The conclusion from the short examination of history is that we basically have to re-think IT as a whole, which is discussed briefly in the next section of the talk. This section first has a look at the new drivers that inflict change on IT. Then it derives the new goals of IT and shows some of the building blocks.
Having this new idea of IT at hand, the role of DevOps in it is finally considered. Starting with DevOps and its continuous pursuit of shortening cycle times in order to optimize outcome, DevOps can be used to drive the change of IT. This is exemplarily shown by starting with DevOps and then see, which question arise from that and what solutions it leads to. In the end of the example, many of the building blocks of the new IT are in place - just by starting with DevOps and continuously improving.
This is a very dense talk covering a lot of ground in order to lead to the final observation that DevOps can (and should) be used to drive the required change of IT and many detail have been left out. Also the voice track is missing of course, but I still hope that it provides you with some useful information.
This is the slide deck of a keynote I gave at Java Forum Nord 2016.
I started with some of the contradictory requirements, developers find themselves often confronted with and the question, if there is a bigger context that we can use to make sense of it.
Then I did a bit of "time-traveling", explaining where we came from and how business and IT have evolved over time. The core finding was that we find ourselves in the middle of a revolution that is going on (not only) in IT.
The last part were some recommendations how an IT developer can at least reduce the risk to become "revolution roadkill".
As always most of the content was on the voice track. But maybe the slides are still a bit helpful on their own.
This presentation shows different innovations in the water sector. It shows examples of business model innovations for household water treatment devices, water treatment plants, or sanitation services. It continues the discussion on business strategies for poverty alleviation within the context of water and sanitation.
This slide deck is basically an extended and updated version of the "Microservices - stress-free and without increased heart-attack risk" slide deck - yet quite a lot of extensions and updates.
The deck is organized in three parts: Why, What and How.
The first part addresses the question if and when you should use microservices at all. It tries to create a bigger picture by explaining changing (business) markets and a changing role of IT and fits microservices into that picture. When looking at this picture it also becomes clear that microservices always should accompanied by other measures like DevOps, Cloud and some more if you really want to leverage its benefits. Otherwise you usually only get the downsides of microservices with harvesting their benefits.
The second part revisits the famous blog post from James Lewis and Martin Fowler, using it to explain what characteristics the microservice architecural style has. It turns out that this post contains quite a lot of information and that quite often only a subset of the characteristics get implemented.
The third part, the "How" dives deeper into the challenges and pitfalls that you usually encounter if you decide to adopt microservices. While of course not being complete and not being a perfect guide that makes everything easy, it should at least help you tho avoid the most common problems and pitfalls.
As always the voice track is missing which contains most of the information (it is a 90 min talk after all), but hopefully also the slides alone contain some helpful information.
Blue Ocean Innovation - From Market-Taker to Market-Maker. This presentation discusses formulating new opportunities for your business or others in a new, refreshing way. Providing you some skills and a toolkit to "arm" you. Helping you become an integrator.
Imagine you are Elisha Otis in the 1850s. You’ve a brilliant idea that a vertical transportation system in a building would greatly help increase mobility and could possibly increase the revenue potential for builders of large-scale buildings. You also had a hypothesis that this technology would be applicable to many use cases, including industrial buildings, hospitals, businesses of various sizes in several industries. You have yet to start a company and build the initial prototypes. You have built a small POC system to demonstrate to potential VCs and investors on your own, but to execute you need capital and a better flushed out business plan.
History has many examples of great innovators who had difficult time convincing their contemporaries of new technology. Even incumbent and powerful companies regarded new technologies as inferior and dismissed it as "toys". Then when disruptive technologies take off they often are overhyped and can cause bubbles like the Internet bubble of the late 1990s.
In this lecture we look at some examples of disruptive technologies and the impact they had. We look at the The Disruptive Innovation Theory by Harvard Professor Clayton Christensen. This explains that new entrant to a market can challenge established incumbent companies. We also look at the Resources, Processes and Values Theory which explains why incumbent companies find it hard to respond.
The hitchhiker's guide for the confused developerUwe Friedrichsen
This talk is basically a successor of the "DevOps is not enough talk", but with a broader focus.
In the talk, after a short motivation, I try to take stock of the current state of IT from different points of view. After looking at, where we came from and where we are, I add the most important trends I currently see that affect us in IT.
But knowing where we came from, where we are and where we are going to usually is not enough. The key point is using this information - in this talk for evaluating your current position as a software engineer and figuring out your desired future position.
As all the details from the first part of the talk make it hard to do this evaluation, I suggest creating a model (actually a framework) on a reduced detail level that makes the evaluation and planning easier. Defining that framework is the third part of the talk.
Finally, the last part consists of some general recommendations that - based on my understanding - help you as a software engineer to stay ahead of the curve for a while.
While this is extremely much stuff (I really consider to split that plethora of information covered in this talk up in several, single-topic talks) and as always the voice track is missing, I still hope that the slide deck gives you a few ideas worth pondering.
Similar to From fixed to relative performance contracts - Keynote by Niels Pflaeging at Cubewise Performance Management Leadership Forum (Sydney/AUS) (20)
Die Erfindung zweier Managements (BetaCodex17)Niels Pflaeging
Wie Follett und Taylor die beiden Schulen der Organisationslehre
ins Leben riefen - und was seither geschah.
BetaCodex Network Associates
Niels Pfläging | Silke Hermann
BetaCodex Network White Paper No. 17 | April 2021 l betacodex.org/white-papers
Deutsche Version April 2022. Diana Mock | Hans Fischer-Schölch | Elisabeth Sechser
The future of organizational learning is discursive & self-organizedNiels Pflaeging
by Silke Herman and Niels Pflaeging.
Workplace learning is not a particularly thrilling adventure these days: Learning in organizations overwhelmingly relies on aged and worn-out formats that produce little learning or impact. The tools in use are often not fit for our time – in terms of content, or learning method, or technology – or all three combined. One cannot help but notice that in the reality of organizations, by and large, Learning & Development (L&D) is a pretty dull affair, clearly lacking innovation. In this paper, we will discuss how that is bound to change. We believe that workplace learning can be as engaging as Maria Montessori envisioned child learning to be, over 100 years ago and as humane, effective and conducive as Ken Robinson demanded in his world-famous TED talks a few years back. Sure, the current reality of corporate learning may look bleak, but there are now signs of a way out of the L&D misery in which most companies find themselves. One of these signs is the platform created by EdTech start-up disqourse.
Work the System – keynote by Niels Pflaeging at Comeleon 2021 (Zagreb/HR)Niels Pflaeging
Why true agility requires transformation of entire organizations. Why meddling with bits & pieces changes nothing. Why real transformation
takes months – not years
The three organizational structures, powers & leaderships: A closer look.
BetaCodex Network white paper No. 18, authored by Niels Pflaeging and Silke Hermann.
The history of management needs to be rewritten. Management science does not, as it is usually depicted, begin with Taylor and Fayol, continuing through the Human Relations movement, in the meanwhile coalescing into the classical school, and eventually diversifying into different post-classic branches. Instead, the history of management is, and has been the story of two distinct, opposing schools of thought that emerged side-by-side, at the dawn of the 20th century. Pioneered by two practical philosophers: Mary Parker Follett and Frederick Winslow Taylor.
Performancesysteme und Relative Ziele (BetaCodex 10)Niels Pflaeging
Warum sich Ziele und unser Umgang mit Leistungsmessung ändern müssen. Wie wir von fixierten zu relativen Leistungsverträgen gelangen – und zu einfachen, ethischen,
Selbstorganisation fördernden Systemen für den Umgang mit Wertschöpfung
Specific ServPoints should be tailored for restaurants in all food service segments. Your ServPoints should be the centerpiece of brand delivery training (guest service) and align with your brand position and marketing initiatives, especially in high-labor-cost conditions.
408-784-7371
Foodservice Consulting + Design
Senior Project and Engineering Leader Jim Smith.pdfJim Smith
I am a Project and Engineering Leader with extensive experience as a Business Operations Leader, Technical Project Manager, Engineering Manager and Operations Experience for Domestic and International companies such as Electrolux, Carrier, and Deutz. I have developed new products using Stage Gate development/MS Project/JIRA, for the pro-duction of Medical Equipment, Large Commercial Refrigeration Systems, Appliances, HVAC, and Diesel engines.
My experience includes:
Managed customized engineered refrigeration system projects with high voltage power panels from quote to ship, coordinating actions between electrical engineering, mechanical design and application engineering, purchasing, production, test, quality assurance and field installation. Managed projects $25k to $1M per project; 4-8 per month. (Hussmann refrigeration)
Successfully developed the $15-20M yearly corporate capital strategy for manufacturing, with the Executive Team and key stakeholders. Created project scope and specifications, business case, ROI, managed project plans with key personnel for nine consumer product manufacturing and distribution sites; to support the company’s strategic sales plan.
Over 15 years of experience managing and developing cost improvement projects with key Stakeholders, site Manufacturing Engineers, Mechanical Engineers, Maintenance, and facility support personnel to optimize pro-duction operations, safety, EHS, and new product development. (BioLab, Deutz, Caire)
Experience working as a Technical Manager developing new products with chemical engineers and packaging engineers to enhance and reduce the cost of retail products. I have led the activities of multiple engineering groups with diverse backgrounds.
Great experience managing the product development of products which utilize complex electrical controls, high voltage power panels, product testing, and commissioning.
Created project scope, business case, ROI for multiple capital projects to support electrotechnical assembly and CPG goods. Identified project cost, risk, success criteria, and performed equipment qualifications. (Carrier, Electrolux, Biolab, Price, Hussmann)
Created detailed projects plans using MS Project, Gant charts in excel, and updated new product development in Jira for stakeholders and project team members including critical path.
Great knowledge of ISO9001, NFPA, OSHA regulations.
User level knowledge of MRP/SAP, MS Project, Powerpoint, Visio, Mastercontrol, JIRA, Power BI and Tableau.
I appreciate your consideration, and look forward to discussing this role with you, and how I can lead your company’s growth and profitability. I can be contacted via LinkedIn via phone or E Mail.
Jim Smith
678-993-7195
jimsmith30024@gmail.com
The Team Member and Guest Experience - Lead and Take Care of your restaurant team. They are the people closest to and delivering Hospitality to your paying Guests!
Make the call, and we can assist you.
408-784-7371
Foodservice Consulting + Design
The case study discusses the potential of drone delivery and the challenges that need to be addressed before it becomes widespread.
Key takeaways:
Drone delivery is in its early stages: Amazon's trial in the UK demonstrates the potential for faster deliveries, but it's still limited by regulations and technology.
Regulations are a major hurdle: Safety concerns around drone collisions with airplanes and people have led to restrictions on flight height and location.
Other challenges exist: Who will use drone delivery the most? Is it cost-effective compared to traditional delivery trucks?
Discussion questions:
Managerial challenges: Integrating drones requires planning for new infrastructure, training staff, and navigating regulations. There are also marketing and recruitment considerations specific to this technology.
External forces vary by country: Regulations, consumer acceptance, and infrastructure all differ between countries.
Demographics matter: Younger generations might be more receptive to drone delivery, while older populations might have concerns.
Stakeholders for Amazon: Customers, regulators, aviation authorities, and competitors are all stakeholders. Regulators likely hold the greatest influence as they determine the feasibility of drone delivery.
Artificial intelligence (AI) offers new opportunities to radically reinvent the way we do business. This study explores how CEOs and top decision makers around the world are responding to the transformative potential of AI.
From fixed to relative performance contracts - Keynote by Niels Pflaeging at Cubewise Performance Management Leadership Forum (Sydney/AUS)
1. From fixed to relative performance contracts
and towards simple, ethical and empowering ways
of dealing with value creation
Sydney, 15.10.2015
Cubewise Performance Management Leadership Forum
@NielsPflaeging
11. Formal part of
value creation
Solution:
Machine
Dynamic part of
value creation
Solution: Man
Sluggish/dull,
low dynamics
high
dynamics
high
dynamics
Age of
Crafts Manu-
facturing
Industrial Age/
Age of
Tayloristic Industry
Age of
Global
Markets
1850/1900
Spacious markets,
little competition
“Outperformers” exercise
market pressure over
conventional companies
Local markets,
high customization
1970/80 today