Are you "on board or out" or "disagree and commit"

Active and passive resistance to changes and initiatives drain energy and morale significantly reducing the chance at success. Poorly managed disagreements can be a project killers. Companies take different approaches to counter this.

Methodologies

  1. Get on board or find another job where an executive decision is the end of the discussion. This approach does not acknowledge that there is a time for discussion and dissention. It forces people to get on the same path while devaluing their role.  
  2. Disagree and commit is an approach most recently made famous by Amazon.  Individuals vigorously disagree during planning and decision making phases. They explicitly commit to the effort once a decision has been reached. 
  3. Create no common framework and operate with a policy of hire smart people and they will do the right thing across the organization.  This can devolve into sandbox style fighting with no obvious path to resolution. I hesitate even mention this guerilla warfare decision making process. 

Choose Disagree and Commit

A well known and broadly communicated decision process provides an easy phrase or framework when it comes time to execute a plan. Everyone understands the implications when they hear it is time to commit. 

 It is important that everyone believe in both phases and their ability to impact the process. Moving from disagree to commit is difficult when it doesn't go your way. It is even worse if people don't think they were listened to.

Not One and Done

Disagree and commit does not mean commit forever. Decisions are revisited and regular or important milestones as part of implementation.  This is an opportunity to revisit previous decisions and change or retain them. 

Comments

Post a Comment

Popular posts from this blog

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaults to a maximum RAM size of 5
Read more

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Update Driver  does  not  install the RNDI
Read more

DNS for Azure Point to Site (P2S) VPN - getting the internal IPs

Image
I wanted to access all my Azure resources without making any of them visible to the Internet.   The easiest give my local machine access to everything on my Azure Virtual Network (VNET) was to connect to it over VPN. It turns out creating Azure VPN gateways and connecting to Azure VPN endpoints is easy.  There are some subtleties in getting DNS name resolution to work that can confuse when first starting out. Setting the Stage There are a few ways to get to Azure endpoints and resources that are blocked from the internet.  We can  Create a Point-to-Site connection from our local machines to Azure Network Gateways Create a Site-to-Site network connection from our local networks to Azure Network Gateways. Use Bastion Hosts Use Cloud Shell Leave everything open to the internet. I chose a Point-to-Site (P2S) VPN connection that connects from my laptop to a VNet Gateway.  That joins my laptop
Read more