The Plan for 2017 and 2018

By David Slight

We'll Talk About Causality and Business Dependency Networks. For a YEAR!

Given our mission to talk about business and technology and learn from diverse perspectives of the group members, we are suggesting and going forth with this self-organizing charter for the coming year. For each of the six BDN perspectives, we will look first at the technology followed by the human perspective. So our calendar for the year looks like the following:

The WHY

November: 

Drivers Tech: what is coming for robotics, automation and futurism

December: 

Drivers Humans: how to evangelize the humanist and people perspectives

Drivers explain why an investment is being made. These are the reasons that senior managers believe will have an impact on the business in a given time frame, yet they are outside the direct control of the organization. A driver requires responses from the business. Drivers can be external (listed first), something in the larger market environment, or internal, an improvement initiative or mandate generated within the organization by senior management.

January: 

Outcomes Tech: What technology and automation do we want to adopt? How far are we willing to let the robots go?

February: 

Outcomes Humans: Define the outcomes we as humans want to achieve.

The outcomes define the end point, or the state at which an investment is aimed.  They are the agreed-upon achievement targets  that help address the drivers. Outcomes are derived from the envisioned changes indicated by the drivers, and help define the benefits that are to be expected.

March: 

Benefits Tech: What benefits can automation and technology provide? How do we measure the benefits?

April:

Humans: Benefits: Who should get the benefits? Large tech corporations or everyone? The developer or sales?

Benefits describe what will happen in the business to help achieve the outcomes. These are advantages to an organization’s stakeholders that can be realized by business changes. Every benefit stream must have an owner who is part of the analysis process. The expected benefits types must be determined, along with how they will be measured. The organization’s key performance indicators (KPIs) are a good source of measures. Inclusion of quantitative measures is preferred, if a reliable number can be obtained from the customer.

The WHAT

May: 

Changes Tech: Where is the tipping point when AI starts to think for itself?

June: 

Changes Humans: Can people change, can culture change?

Business changes are new and permanent ways of working within the organization to realize benefits.  The changes come in three forms: 1) Doing new things, 2) doing things better, and 3) stopping counterproductive things.  These can be shown at a high level in several ways, depending on the organization’s preference: as a business process to be changed, a description of the changes to be made, or as organizational capabilities or functional units.

The HOW

July: 

Capabilities Tech:  What capabilities can we rely on from technology?

September: 

Capabilities Humans: What are the essential human capabilities that should be retained and nurtured?

Capabilities are that must be at the required level of maturity in order to support the desired business changes. Multiple capabilities may be required to change an individual process, and some changes may affect more than one process. Training, implementations of new standards, policies, and procedures, or acquisitions and reorganizations are included in this category.

October: 

Enablers Tech: Which technologies are ready for prime time?

November: 

Enablers Humans: What can technology still not enable?  

Enabling technologies  provide the lowest level answers to the question of how  business changes will be achieved.  The items in this column are the IT systems, projects, or product features that will support needed changes. They can support changes in a business process, as well as the introduction of new technology or the work required in a project .

WRAP UP

December: Discuss our charter for 2019

AppsJack Group to Change World in 2018

It was a nice Fall day and the biggest and best turnout to date happened for the AppsJack group last night at Big Fish Grill in Kirkland.

Alan Andersen, Andrew Sengul, Berry Zimmerman, Christian Harris, Dominic Wong, Dr. Tom Louwers, Ele Munjeli, Eric Veal, Jean Bishop, Jehan Bharucha, Kifaya Dawud, Mark Mueller-Eberstein, Megan Gaiser, Thomas Mercer, Mike Dodd, Reba Haas, David Slight, Sriram Sabesan, Steve Kubacki, Susan Stringer, Richard Webb

 Here was our agenda for the evening:

• Retrospective and feedback
• Success stories and new relationships from the group
• Best parts
• Worst parts
• Things to change
• Competition - what takes you away from it?
• Purpose and identity - who are we and why are we here, what's our name?
• Schedule and frequency, meeting types and formats, size of meetings
• 2018 Topics
• Ongoing relationship to APQC?
• Organizers / board
• Expansion, scope, milestones, organization
• Fees
• Partnerships, sponsorship, affiliations
• Podcast
• Subgroups and committees
• Technology, tools and online presence
• Venues, Seattle

Here are the main action items and to do's from the meeting:

• Plan in detail
• Change name
• Remove cap of # attendees
• Postpone start by one hour
• Change topics from APQC to BDN + Robots + Humans in 2018
• Get owners/hosts/leads for each 2018 meeting 
• Look into online tech that would help
• Book reviews
• Pre-reading and recommendations
• More detailed profiles for each member - stickers or badges based on the APQC model
• Patreon platform for contributions
• E2B as sponsor?
• Consider and help each other develop what "product" each of us is creating
• Opportunities to share stories and successes annually - a gala
• Leverage what is unique and beneficial about Seattle over other tech hubs like Silicon Valley - be unique, different and stand out.  We are practical and not Hollywood.  We are loggers and fishermen.

And here are detailed notes, outcomes and decisions from the meeting.  Join us at a gathering soon!

• Retrospective and feedback
• Lots of good feedback here.  People were here for:
• "High level thinking"
• Diversity of opinions and perspectives (learning)
• Academic, experienced and educated tone
• Consistent high quality
• Stimulation
• Idea sharing
• Cross-domain thinking and experiences, feedback and ideas
• Random networking
• Stories and experiences are illuminating
• Successes people have had
• Steve and Andrew met through the group and are collaborating
• Christian has met a ton of new people through it
• Thomas met Bruce Follansbee who has opened many doors
• Purpose and identity - who are we and why are we here, what's our name?
• Brainstorm on names, taglines and descriptions
• Descriptions and Taglines
• Thought provoking
• "It's all connected"
• Making Meaning and Money
• Names
• Think tank
• "Talk Tank"
• "Food for Thought"
• Talk, Inc.
• Rethinking business
• Humanist Technology
• Making Business Human
• Saving Business
• Business Humanity²
• Human Tank
• Business Reconnected
• Business & People Reconnected
• H2H: Human to Human
• Unf*ck Business
• Human-Centered Business
• Business Renaissance: Unf*cking Business - This was the most popular (or at least the funniest).  We will continue to think about the best name.
• Schedule and frequency, meeting types and formats, size of meetings
• 4th Tuesdays will continue
• 5 PM official start preferred but people welcome to show up earlier
• No limit on number of guests
• "Owners" / organizers for each meeting - sign up sheet
• 2018 Topics and themes
• Ele: "The automation apocalypse"
• AI vs. Automation
• Robot-Human Interface
• Steve offered this three-pronged approach:
• Economics
• Business
• Praxix / Products (concrete)
• Zodiac signs - Andrew Sengul
• The BDN model with David Slight: Drivers, Objectives, Benefits, Changes, Capabilities, Enablers and then switch between the tech/robot perspective and the human perspective.  
• Ongoing relationship to APQC?
• Nothing will be overt.  Could come up again here and there but it's over for now.  RIP APQC!
• Organizers / board
• Not needed.  Tap individuals as needed.  Build small, focused teams as needed.  Keep organic.
• Expansion, scope, milestones, organization
• Happy to keep it as an Eastside only event for now.
• Eric will talk to Michael Dodd and the Product Camp people about expansion of a group in Seattle.
• Fees
• Keep it free / optional.
• Can charge through meetup.  Runs the risk of turning people away; traction is preferred to profit.
• Some guests are willing to contribute capital.
• Partnerships, sponsorship, affiliations
• Keep this standalone for now to maximize flexibility.
• Podcast
• Yes, the podcast is good.  Keep it tied to the meetup on the same schedule.  Add 1:1 podcasting capability through Janis' Machala or Josh Golden's contacts.
• Subgroups and committees
• No need for this right now.  Will form as necessary.
• Technology subgroup: Ele, Andrew, Eric
• Technology, tools and online presence
• No agreement here.
• An online discussion forum could be good.
• Will talk with Andrew and Ele to decide on a direction.
• Venues, Seattle
• Big Fish Grill fine for now.
• Reba and Berry may have some functional options if we want to switch it up.

About Vision & Strategy - How to develop it, other challenges and considerations

We had a motley crew of awesome people show up to the AppsJack Share gathering last in Kirkland to talk about Vision & Strategy. I got a lot of great input (see everything below) that will help me better direct the January version of the podcast.

Key Takeaways:

1. Strategy and approach (what to do) depends on the stage and situation of the business
2. Work Breakdown Structure (WBS) a good way to break down complex projects
3. Internal and external lenses/views/perspectives key to understanding and thinking about strategy
4. Personal and corporate authenticity key to successful implementation
5. Aligning an essential skill
6. Nuance and readiness for seeing, understanding, integrating and working with outliers and anomalies is another key
7. Timeframe matters for strategic thinking
8. Context matters (and therefore controlling/limiting scope and having focus)
9. There is a general prerence toward rapid tests of assumptions (failing fast) rather than long and protracted 'strategic' actions but there are times when the latter tactics (strategic actions) matter
10. We couldn't determine whether or not models mattered. Models are meant to be broken, so why manage to them or even think about them?
11. The mitigation and reduction of risk is key to successful strategy
12. Design thinking is a key and related skill
13. Strategy isn't and shouldn't be thought of as linear

We wondered at the very beginning if we should start by discussing vision or strategy and the answer, perhaps not surprisingly, was 'it depends'.  Chris brought up a good point that it very much depends on the stage, phase or status of the organization.  Assessment and triage (qualification) is first needed.  Steve raised challenges he has about breaking down a compelling vision into the component parts.  To me, these are the skills of project managers and other leaders who make complex and challenging things easier, that can be communicated to the necessary suppliers.  Work breakdown structure is a common method.  Mike Pritchard shared that he thinks there is an internal and external vision.  Joe Okonek refers to the vision, values and valued behaviors as things that can / should be externally communicated and publicly shared.  Missions, for example, can be internal documents and communications that help internal relationships focus on comm and strategic goal.  Public/open and private/closed is another dimension on which to explore strategy.

Good parts / what attendees liked: mentions of sex, swearing, arguments, passionate discussion, British accents, food, beer.  Authenticity was brought up as a key factor in this area.  Without true authenticity (and value, quality) your audience will see you as a fake and disengage (won't authorize).  Berry talked about the importance of alignment.  For example, aligning yourself and your company with the market and environment and their vision, values, purposes, needs, interests, ideas, etc.  Dominic talked about the difference between power (which can be personal and thought of as influence) and force, which can be applied from the tops down if someone has a lot of money or ability to coerce.  10 types of power are discussed in this article.  David brought up the point that strategy usually requires a longer and more futuristic timeline.  For example, he said that it's hard to be strategic for two minutes.  

Dominic led us in a discussion of the definition of a strategy and there were many different thoughts and opinions.  Someone defined a strategy as choosing an approach or an approach chosen ie a decision and commitment was necessarily made. I brought up the notion that it is hard to create a perfect product but many people disagreed: that within a domain, there can be a perfect product.  But there is a context, and knowing this context well is critical for product success.  Dominic wanted us to separate 'strategy' generically with 'strategy with a purpose' (a clear why). I brought up an issue I was having at work making a decision to build a feature for a big customer or not.  I am in the process of determining whether their request is qualified or not.  There is much skill required in qualification of certain issues.  Many at the table believed that 'if you are going to fail, fail fast' and people didn't like the idea of dragging on some elaborate process but others believed that caution and due diligence, not just action, were required in certain ambiguous political situations.  There are also scenarios where people cannot afford to fail fast, especially when there is not yet a powerful coalition, agreement and a clearly articulated and communicated vision.  

Richard wanted to know, "How do you know you have strategy?"  It's a good question.  We agreed that force, power, belief, authenticity, conviction and in many ways consistency were required for strategy.  But flexibility and other leadership qualities are also required.  We talked for some time about whether models were important or not.  David did not believe they were beneficial.  I gave the example of NoSQL database strategies where the data gets stored independent of a rigid table schema.  Many new data storage strategies do not rely on a centralized schema.  Differences between abstractions and concrete proof, evidence or data were interesting.  "Insight" or mental models are interesting when derived from data or science.  Steve talked about millennials and their needs.  He says that they share a desire for a better world and have this impediment of the rest of the world who is still alive, their elders.  

Someone pointed out that it is important to seek out anomalies in your data and to test assumptions.  Andy Scott made the point about the import of assumption testing on Episode 2 of the podcast.  Assumptions are a category or area of risk.  Steve shared the saying, "The presumptuous assume, the sumptuous consume."  People do need to build and test (at least mental) models.  Jean brought up the saying to test early and test often.  I shared about test-driven development (TDD), which is about only writing enough code (doing enough) to pass the next test.  It is a Lean approach.  Richard talked about the Site Reliability Engineer (SRE) role at Netflix and how they have build their strategy and plan around mitigating risk.  Managing and reducing risk is a key element of good strategy.  We talked a lot about design, design thinking and its import and spent quite a bit of time talking about Steve Jobs as a visionary and who else he surrounded himself with that helped make him successful.  It was suggested that Jonathan Ive at Apple was very critical to Steve's success and controlled and manipulated him in many ways.  He did of course have many failures as well.  Someone shared the idea of designing for failure, not success.  

Dominic wanted to make it clear that strategy was not linear and that it runs off of principles related to non-linear dynamics and non-linear systems.  Berry shared that it is our intention as managers to create systems that control and constrain--and this is necessary--but does indeed rub up against the truly dynamic nature of people and systems; feedback loops and quality systems that continuously transform and improve systems are indeed required.  We talked about automation and its important and how design decisions like 'who does what' plays big-time into strategy.  In my opinion, users should be the preferred and default / de facto actor and some (many?) of them should have the option to do a task themselves (value add) or delegate a task to a computer or someone else.  We started talking about the podcast toward the end of the event and Bruce recommended The Boss Show, which is a Seattle-area recording about bosses.

Berry posed the question, "How do you know that your vision is not a unicorn?" which is basically to say that you are not living a delusion or tilting at windmills.  The book Black Swan was recommended.  Richard talked a lot about the many types of currencies which relates to the idea of non-monetary economies.  I wondered out loud and Steve agreed that there is some sort of harmonic mathematical equation that describes a leader's oscillation between hypothesis tests and failures.  Bruce brought up 7 Habits of Highly Effective People by Steven Covey and I mentioned that The 8th Habit is about "finding your true voice and helping others find theirs".  The book also talks a lot about connecting strategies of the head with those of the heart which is probably truly about authenticity, believe and conviction.

Questions and topics for further consideration:

• A Strategy (noun) vs. Strategy (verb) - What are the differences?
• The skill of qualification; how to qualify, what to qualify, what to ignore?
• Modern automation thoughts - who does what and what to do with the displaced workers?
• Why do the ideas of internal/private/closed and external/public/open help us in thinking about strategy?
• How do you know you have strategy?  (What is strategy?)
• What are the differences between real-world models and mental models and/or thought processes?  
• Test-driven design in management?
• The applications of flexibility and rigidity in strategy development

Which topics, ideas and points would like to see covered on the podcast about Vision & Strategy?