Showing posts with label business. Show all posts
Showing posts with label business. Show all posts

Wednesday, July 31, 2019

Is Subscription Pricing Fair?

Image result for pricing

Is subscription pricing fair to those involved? Who typically wins and who typically loses in these schemes, the seller or the buyer? 

Subscription is defined as:

"the action of making or agreeing to make an advance payment in order to receive or participate in something."  It should also be added that subscriptions typically happen on a recurring basis.

Modern subscription pricing models give discounts for longer commitments where paying and renewing per-month, for example, is more expensive than paying or renewing on an annual basis.

What is driving buyers (businesses as well as consumers!) to decide to pay for a subscription?  Sometimes it's the only option available.  Some of it can also be explained by FOMO (Fear of Missing Out).  The opposite scenario, would be grandpa Murray's saying, "Tell me what you need and I'll tell you how you can get along without it."

Here is what is driving the move to subscriptions:
  1. Limited choice. This affects both seller and buyer.  Barry Schwarz has been absorbed, but the result is sometimes perversion of the intent.
    1. Seller – Offer buyer fewer choices to make the sale faster, train sales people on “value” of having all options available
    2. Buyer – Less to think about
  2. Don’t need to worry about a varying usage pattern.  Big decisions up front (sports or not in package), but then it doesn’t matter if there is a sleep over.  At a business level, I may not be using a specific feature now, but it’s expensive to add.
  3. Aspirational.  If I pay for the gym I’m more likely to guilt myself into using it.  If I buy a media subscription, I may come back to read it later, and I know it’s much more expensive to buy single copies.
  4. FOMO.  Perhaps.  Water cooler talk about a new show?

We further dissect the elements of subscriptions:

Ease. The ease or simplicity of subscription pricing can be quite disturbing: in a 'set it and forget it' fashion, consumers basically sign up for services that they may never use and grant an annuity payment to the seller if their subscriptions go unmanaged.  It's interesting to wonder how many subscriptions people have versus those that are actually used.  The difference represents waste and likely profit for the seller.

Popularity.  Subscriptions likely take up an increasingly large mix of consumers' market baskets.  This perhaps relates to the previous concept and the perception of abundance: and it is generational to some extent. Taking care of the pennies and the dollars will take care of themselves has been replaced by “it’s only $25 per month” and buyers forget how much all the $25 adds up.

Partiality.  Rather than paying for the entire value of the item up front, in subscription pricing, it is like leasing or renting: it creates a price that may seem more affordable or attractive to the consumer and makes the buying decision easier.

Waste on the Consumer End.  There can be waste for consumers of subscriptions: we sign up and don't use them. Magazines arrive, for example, accumulate and don't get consumed. Subscriptions if used well directly align supply and demand but when the buyer does not make full use of the subscription and its benefits, there is misalignment and therefore waste; the system can be inefficient.

Waste on the Seller End. There are also examples of waste where the company gets the model wrong and loses: a recent example of this was MoviePass who offered for $9.99 nearly unlimited access to movie theaters.  The company quite famously experienced major challenges with this model and folded badly.  Fast followers and larger, more established organizations like AMC quickly swooped in on the opportunity and figured out a set of economics that could more sustainably provide a subscription service to this market.

Returns.  When there is waste it may be the duty of the seller to both detect and re-adjust the subscription plan to better fit the usage pattern of the user. An example of this is cell phone carriers who are willing to recommend a better plan based on the observed usage of the service by the user.  Consumers will expect and want more of this kind of governance and value.

Options and Complexity.  Another common example of waste in subscription models and a "good thing" for sellers are gym memberships: consumers keep paying regardless of use.  Gyms would perhaps be delighted if their members never showed up as long as the revenue stream kept flowing.

Option Time Frames.  Options can be offered in both "pre-facto" and "post-facto" contexts.  For example, in the pre-facto sense, consumers can choose whether or not too add cheese to their burger. This is a competitive differentiator for some: have it your way vs. limiting options by policy because the seller knows what their consumers like.  An example of a post-facto (after the purchase) option would be returning the burger for a full refund if unsatisfied.  A better example, related to subscription, is a refund for unused services or carry forward minutes, as it were.  Carry-forward is not necessarily in the buyer’s interest if they aren’t going to binge to catch up.  This also happens in employment scenarios when employees accumulate "sick days" that expire at the end of the year.  Have an inexpensive service where what the consumer pays seems worth the price, but it's messed up if it's only used as a small fraction of the number of available annual uses.

Increasing Complexity.  It is likely that pricing models will only increase in terms of their complexity over time and this will lead to increased confusion and dissatisfaction of consumers.  End-User License Agreements (EULAs) of software, for example, are notorious for their complexity and consumers are known to just skip over them rather than understanding the language and implications of their engagement with the offering.  Consumers are likely to get tired and "don't have time to do a spreadsheet every time they are going to buy something." There used to be a place for consultants between business buyers and vendors – interpreting what the prospect really needs.  Computers are driving this innovation and ability to deliver more complex mechanisms successfully.

Overwhelm.  In Barry Schwartz's The Paradox of Choice it is argued persuasively that not everyone needs or wants more choice and at some point the buyer becomes overwhelmed with options and relies on gut, emotion, bias or instinct to decide.  From an engineering and innovation perspective more options,  bells and whistles are valuable but it is the job of the marketer or product manger to bundle and package only these innovations into bite size chunks that the end users will actually use, consume and from which they will, at scale, actually receive value and benefit.

Base Plus and Hybrid Models.  Some new pricing models start with the base service and then offer add-ons or subscriptions on top of the base capability.  These can be thought of as hybrid models with fixed and variable expenses.  As if lots of features and pricing models were not enough to confuse the consumers, "modes" and options of features (like colors) add yet another layer of complexity to considerr.

Bundling, Tailoring and Customization.  Rather than one-size-fits-all strategies, companies are starting to play with services that better fit the consumer. Although a side effect is too much choice for the consumer, one benefit is (if the choices can be simplified) that the services and prices can be directly tailored and fit to the needs of the buyer.  There are opportunities to tailor based on buyer psychographics that aren’t being fully utilized, for example, as well.

Returns and Less than Full Utilization.  Return  policies in some way are linked into pricing benefits, perceived value and purchasing decisions.  For example, some snow chains can be returned years later if not used for full money back.   Organizations like Costco and Nordstrom are known for great return  policies.  There could be scenarios in subscription pricing models where the unused portion of the service could be returned for all or a portion of the money back but these seem rare today.  Said differently, rather than consumers having to 'eat' the difference, the seller could detect unused capacity and give the consumer some money back, making the exchange more efficient and less one-sided. Another example of seller graciousness and service is Les Schwab changing unused snow chains for those fitting a new vehicle.

Lack of Ownership.  Traditional, basic pricing models of music, for example, where an entire CD
is purchased and owned may also demonstrate waste but the goods at least become an asset to and property of the buyer.   Possession and ownership also provides the ability to transfer, trade or sell the item post-facto and buyers can recuperate some of the cost.  Leases, subscriptions and downloadable music do not typically exhibit an ability to transfer. Perhaps an album as a coherent offering from an artist whereas streaming services muddy the waters.

Delivery Method.   Many new delivery models are available today as well, which also play into consumer perception of value.  For example, Amazon  Prime's home delivery and one-day delivery are extremely convenient for users and create excitement.  Similarly, Amazon now does delivery to vehicles, garages, and lockers. Innovation in delivery can be captured in pricing.

Customer Service and Trust. The quality of customer service and in some cases access to human representatives of the organization also plays into consumer thought on value and price.  Painful customer service experiences, ridiculous hold times and no access to qualified and capable humans is largely dissatisfying for consumers, resulting in customer loss.  What is driving consumers' perception of trust in providers?  The relationship and perception of care and personalization is a big part of it.   For example, Verizon and Pemco keep good records about customers so the relationship with the organization is maintained over time building trust.  Some businesses calculate Customer Lifetime Value and tailor services based on the perceived (most likely remaining) value of the customer.  There are of course examples where the provider bends over backwards and goes above and beyond what is reasonable to delight a customer or prove a point in the market.  The book Snow Crash by Neal Stephenson tells fictitiously of a Pizza Company CEO who travels to the dissatisfied customer to apologize in person for a poor delivery, then harms the delivery person.

Justice and Equity.  When both parties feel like they have compromised an equitable amount or given up something of equal value during the exchange, interests are aligned and growth can flourish.

Geography, Regulatory Context, Risk-Transfer and Taxes. Sales taxes and their avoidance also plays into product pricing strategies and distribution methods.  In the Supreme Court case of South Dakota  vs. Wayfair, it was ruled that, "states can  mandate that businesses without a physical presence in a state with more than 200 transactions or $100,000 in-state sales collect and remit sales taxes on transactions in the state."

Criticality for Businesses.  Not only are companies thinking about how to avoid tax expenses, they're also thinking about how to best finance their operations.  And what better way to get cash in hand to fund future activities than to get recurring payments from consumers rolling in?  This is one of the key reasons for subscription pricing, and also results in many of the problems and examples of misalignment.

Buyer Beware.  From an early age, as consumers, we are hopefully trained to question what is being sold and marketed to us both in terms of value, price and supplier quality.  As consumers we are raised in a culture of skepticism and a lack of trust for sellers and sales people, for example.  Other cliches abound such as The Customer Is Always Right.  And in practice that principal is not regularly honored.

To Summarize a Few Points:



Special thanks to Mike Pritchard for his great edits and additions to this body of work.  And to Carrie Dugan, Larry Gales, Berry Zimmerman and David Slight for their awesome contributions, experiences, knowledge and ideas.

Please join us next time for a dinner conversation and following article that will address the question, "Is Automation Progress?"

Saturday, March 31, 2018

The AppsJack Way

Image result for team building

My first real business project was in 1996 when I built a marketing website for my dad's business, Anacortes Brass Works.  ABW sells large runs of belt buckles to businesses, primarily, and the website was a real boon.  It was a fun project.

Through the nineties, friends and I built a lot of websites to learn the new medium. 

From 2000 to present, I work by day in the Fortune 10 as a business advisor.  My skills are technology and transformation.  I work with some of the largest brands in the world to figure out how to use more data and education to transform and mature their businesses efficiently.

On the side, I love helping local entrepreneurs advance their causes.  There is Chris, Pete, Lee, Ted and many other friends who I've been lucky to help  move the needle on their ideas and their careers.

I'm not a coach, exactly, but I think I am motivational; at least I've been told so.  I have master's degrees in Information Systems (business + the internet) and Business Administration.  I am a certified Project Management Professional.  I have been doing business consulting professionally since 2005 when Siemens Corporation made me an internal consultant.  And realistically I have been helping businesses grow and advance since high school when I first started to understand my parents' businesses and their associated challenges.

Last year, on the side, we helped a local businessman named Ted Clark reinvent his data service business.  Ted was  providing a variety of services to people but with no real direction or theme and found it hard to build up a pipeline of clients.  He wanted to figure out how to better market himself.  With a partner, Steve, who was good at marketing technology, we worked with Ted to devise ways for Ted to target clients.  We selected users of the popular Shopify online store and refined the market even further from there.  With that project, we helped Ted identify his target audience, hone is products and services and provide a unique service that scaled.  Ted's sales increased greatly and he's been able to grow his business much more easily from that point forward.

AppsJack's latest project is working with a Woodinville-based friend, Lee, to scale his new business called Shape My Grip.  SMG has a patented grip for bicycles that will hopefully eventually move into other sports and healthcare applications.  A partner, Sebastian, and I are coming in as business consultants to sell more of his products faster, using Amazon and Fulfillment by Amazon.

AppsJack is best at providing product management services to its customers.  We help them understand their market and defined products and product releases aimed at capturing A) money and B) knowledge about what people want.  We drive hard to advance product development and innovation. 

We partner with business owners to accelerate their sales and advance their careers, all in the name of fun, partnership and profitability.

Many people are not very confident marketing themselves or their products.  It can be nerve-racking and stressful.  We partner very closely to support our clients, make them feel good, make them feel confident and help them make the right decisions to mature their products and move their businesses ahead.

AppsJack works with a very high sense of urgency and the latest technologies to define and advance the agendas of our clients while skillfully mitigating key risks.

The requirements for pulling off this kind of services business at scale are:

  • A great team.  We have a network that includes some of the most amazing talent around in all fields of business development from hard to soft skills in all industries.
  • The best from technology.  None of this would be possible without technology.  We stay abreast of the latest technologies and implement where and when we can with out clients.
  • Clients who inspire us.  Our clients come from a variety of walks but are generally seasoned business people who are ready to go out on their own or advance a product or service they have already started.  We work with them to help set the vision, understand the impediments and give a huge boost toward their goals.
  • Flexible compensation arrangements.  We are willing to work for profit-sharing, for example.  So that clients don't have to stomach huge up-front costs as we get going accelerating their business or project, we help align on incentives for everyone to win.
  • Unusual focus on community.  AppsJack organizes regular meetings and spends a lot of time out in public, including volunteer work with great causes.  

Contact us today if you'd like to hear more about our project and what we're building here in Seattle and the Eastside.

~ Eric

Friday, March 2, 2018

The Latest in e-Commerce Tools, Tech and Techniques from Pros in Seattle

Image result for e-commerce

We showed up at an e-Commerce Meetup in Seattle last night and learned a lot.  The group is called Seattle Profit Pirates Mastermind Group - Ecommerce & Amazon Entrepreneurs and was meeting at a coffee shop on Capitol Hill.  We got a lot of tool and tech recommendations and met some thought leaders in the field.  Here are some details for all you e-Commerce and digital marketing people out there.

Terapeak shows you what to sell online.  MerchantWords helps you find more buyers.  Google Adwords is a classic and key tool.  Many people use Facebook to create ads and funnels.  Text / SMS is another technique for capturing emails.  Shopify was considered to be the best e-Commerce tool.  James who runs Wooly Clothing and was telling us about Amazon's practice of  Brand and Category Gating.  Benjamin, who runs the group, was asking about Liquidation services.  He said he's tried FoxBox.  I mentioned Alternativeto.net as a method of finding technologies in a category to support a business process or function. 

We didn't talk about but I was reminded of Mautic, HubSpot and my buddy with Conversion Wizards.  Benjamin says it's important to consider Cost Per Email as a metric.  He also mentioned that MailChimp has an advanced, for pay, feature that provides additional metadata for email addresses to extend marketing.

James was asking about managing multiple channels and Benjamin swore by Skubana, a multi-channel inventory management system, which is $1,000/mo.  He says it's well worth it if you have the volume. 

Flexport, a freight forwarding method, and Keepa, an Amazon price tracker, were also mentioned as useful tools. 

Thanks to all attendees.  Great event and lots to learn.  A whole new domain and area to explore.

Monday, December 4, 2017

AppsJack TECH DRIVERS Debate Highlights - November 2017

We had a motley crew of 16 awesome people at the kickoff of AppsJack Season 2, where our topic is causality and business dependency networks (BDNs). 

Image result for the matrix

We were led on Tuesday evening by management consultant David Slight who is basically awesome. David came very well prepared with handouts for the guests and a meetup host sign-up sheet.  David led us in topic 1 of 12: TECH DRIVERS. 

The dialog went far and wide and was fascinating.   The discussion touched on:
  • The 3rd Industrial Revolution wiki
  • 5G mobile networks wiki
  • Humans are Under Rated video
  • GM says it is leaving the automotive industry - Richard Webb statement, needs source
  • Bonini's Paradox - contribution by newcomer Lucas Parker - "explains the difficulty in constructing models or simulations that fully capture the workings of complex systems (such as the human brain)."  wiki
  • "Things don't just happen, they happen for a reason."  ~ David Slight quote.
  • Drivers are things we can't change.
  • Richard spoke about the technology having been ready and done for five years but regulation and its impacts are the things holding its implementation back.
The main lessons that I took away as a facilitator and leader of this group were A) we need to tell people to create a small team of at least one other person so they are engaged and can break out if needed (and not just be quiet or disengaged in the discussion).  Having small groups is one thing that makes us identify as part of the big group.

Join us for our next gathering in a couple of weeks when we'll take the HUMAN side of the DRIVERS debate.  Details and RSVP here.

Tuesday, November 14, 2017

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

Wednesday, October 25, 2017

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.

Monday, October 23, 2017

AppsJack Capable Communities Podcast Season 1 Completes - Check It Out

We started out with this idea and framework and made it work.  Congrats and thank you to all involved.


It's amazing!  We just finished year one of the AppsJack Podcast: Capable Communities.  How awesome does this feel.  We had this idea a couple of years ago so it's amazing to see it come to frution and be so fun.  

Huge thanks to producer Christian Harris for all of his time and grace, Steve Kubacki for awesome support and content, Ele Munjeli for being so great, Richard Webb and David Slight for their amazing contributions.  We've truly built an amazing community and I am so proud.  

The Season 1 guests are listed below in alphabetical order.  We recorded 30 episodes with 30 guests and published over 16 hours of content, covering each of APQC's 12 areas of business processes.  We ate a lot of breakfasts and brunch, drank a lot of coffee and beer.

Tech Staffing CEO Aftab Farooqi
Leadership Coach Alan Andersen
Lean Agile Fellow Alan Sebring
Smartsheet Developer Andrea Cremese
Developer Andrew Sengul
Executive Andy Scott
Podcast Producer and Real Estate Mogul Christian Harris
Creative Data Genius Dave De Noia
Finance Expert and Restaurateur Dave Niederkrome
Security Expert and All-Around Brain Don Alvarez
The Inspirational and Motivated Ele Munjeli
IT Champ James Murray
Entrepreneur and Sales Professional James Tuff
CEO Joe O'Konek
Startup Attorney and Podcaster Joe Wallin
Patent Attorney Jonathan Olson
Security Expert Josh Barrow
Front-End Developer Josh Bosworth
International Marketing Wiz Kifaya Dawud
Tech Consulting Business Developer Lee Carter
Startup Wonk Leo Lam
Crypto Currency Consultant Mark Mueller-Eberstein
Author and Speaker on Focus and Clarity Michael Cavitt
Author and Conflict Management Specialist Rachel Alexandria
Lean PM and Business Continuity Expert Ralph Kliem
Business Attorney Reuben Ortega
Architect Richard Webb
CEO and Member of the Board Scott Davis
Clinical Psychologist and Very Creative Steve Kubacki

Stay tuned for what will happen in Season 2!

Wednesday, August 23, 2017

APQC Acquire, Construct and Manage ASSETS and Mega Project Management Meetup Summary



The business group met at its usual place and had a good turnout. The topic was Acquire, Construct and Manage Assets and I wanted us to explore 'mega projects'.  It was summertime and I hadn't promoted the event much but we had some old faces show up and some new blood as well.  In the house for the first time was Sri, a friend of Richard Webb's, and an incredibly sharp and talented management consultant.  Our topic for the evening was 'Mega Project Management Techniques' and it was within the context of APQC PCF's Acquire, Construct and Manage Assets category.  For fun, Richard and I sat on opposing ends of the large table so we could battle.

We had a $150 + tip minimum we had to meet so attendees were encouraged to eat and drink to their heart's content.  I enjoyed two IPAs and even sprung for the Filet Mignon (medium rare, of course), which was served with broccolini and I got fries and there was a slight truffle flavor happening somewhere on the plate, which was good.  Overall the meal was quite good, although the filet did not compare to the quality available at Jak's.

And so our discussion of ASSETS began and Richard, as is somewhat typical, took the lead and shared what he knew and thought about the topic.  Also in attendance were yours truly (Eric Veal), Bruce Follansbee, Thomas Mercer, James Murray (thanks for showing up, James!), Alan Andersen, Steve Kubacki.  Richard's friend Sri arrived toward the end as we were closing up shop.

Thomas offered that assets were rent producing.  We were working on a definition of asset that we could all get behind and I was also preparing for the recording in early September of the AppsJack Capable Communities Podcast on the Asset Management topic.  We wondered if assets were investments and thought they may need to have a positive ROI.  I suggested that assets created passive income.

We discussed the modes of acquiring assets: with cash, by making them, and by financing them through other means.  Richard talked about two main classes of assets: Cost of Doing Business Assets (like printers, for example) and Intellectual Property assets.  We wanted to keep drilling down on the definition of assets and more fully understand their properties and methods. So we did: we wondered if assets had a property of technical debt and we spent quite a bit of time considering if technical debt was an essential property of an asset (since assets, like anything, are probably not perfect).

The conversation shifted from technical debt (bad design and things requiring rework, really anything imperfect) to the role of the architect as the key person who creates and hands over assets.  Richard, who has been an IT architect for years had many things to say about the topic.  Richard shared some stories with us including a multi-million dollar project where he and the team dropped off a very large stack of documents off to the client about how to make a data center.  He described the pile of paper being feet-tall and the 'thud factor' of dropping off all that intellectual property to the client.  Richard pointed out another distinction in that 'only humans create IP'.  He described assets as an object with a unique ID, that they are "sellable" and containerized.  Assets have clear scope and their boundaries (what they are and are not) are well defined.  Richard wondered if there could be an Operating Expense asset and we discussed the new billing models with the cloud where people are renting services.  We also spoke about the cloud as a utility and some issues relating to the regulation of the cloud providers by providing some sort of efficiency index.

Examples of Goldman Sachs' position in the market came up for the second time in as many weeks.  On the last podcast episode, guest Mark Mueller-Eberstein made some guesses about how Goldman could enter into the crypto-currency space. Studying more about Goldman could be a good thing as for innovation.

James pointed out that business brokers use the formula EBITDA x Risk to get the business value.  So risk (in our case technical debt, for example) is a fundamental aspect of reducing the value of a firm.  Getting to a reasonable risk quotient is a trick.

We debated issues of "boutique services" and wondered how one-to-one services like Alexa and Google Home would be regulated in the future.  Richard shared about three key properties of modern software services, a subclass of asset: UX, Adoption, and Consumption.  The consumption part is what is metered in modern systems such as Microsoft Azure and Amazon Web Services (AWS).

Bruce cited the book Fumbling the Future about Xerox's fall from its central role in office automation.  The group also had a long and detailed conversation about practices at Boeing.  Someone in the group stated that, "Boeing doesn't make ariplanes, it moves money."

Join us soon for podcasts on the Managing Assets topic and join us at the meetup in September when we will discuss Risk, Compliance, Remediation and Resiliency.

Friday, June 16, 2017

Podcast Recording Summary - June 10th, 2017 - Developing & Managing Human Capital

Last Saturday, June 10th, a group of us gathered to record the Human Capital episodes of Season 1 of the AppsJack podcast.  We were very pleased to be joined by such a large and awesome group.

On the Upcoming Episodes:

Aftab Farooqi
http://linkedin.com/in/aftab-farooqi-693a09b

Rachel Alexandria
http://linkedin.com/in/rachelalexandria

Lee Carter
http://linkedin.com/in/gleecarter

Joe OKonek
http://linkedin.com/in/josephokonek

Steve Kubacki
http://linkedin.com/in/steve-kubacki-18750936

Andrea Cremese
http://linkedin.com/in/andreacremese

Eric Veal
http://linkedin.com/in/ejveal


Episodes Recorded:

Develop & Manage Human Capital - Taking Risks at Work

The group delves into Risk-taking at work and how individuals can take risks without risking getting fired.

Develop & Manage Human Capital - Managing Through Crisis

The group delves into Dealing with Crisis at work, led by Joe OKonek.

Develop & Manage Human Capital - Organization Health

The group delves into Organization Health, how to think about it and methods of studying and improving it.

Develop & Manage Human Capital - Conflict

The group delves into Conflict at work and covers ways to avoid, cope and manage through conflict, led by expert and author Rachel Alexandria.


AppsJack will release a new episode every Sunday starting in June!  Tune in.

Wednesday, May 24, 2017

Developing and Managing Human Capital - Notes from the May 23, 2017 AppsJack Business Services Meetup in Kirkland, WA


"Human Capital" was the topic to be discussed.  It was a sunny late-May afternoon and I headed down to Big Fish Grill to have the discussion with about 10 others who had gathered.  Unlike the normal gathering, we were given a smaller table, which in the end wound up being a little better: cozier and easier to hear people.  We never broke into smaller groups and had a good dialog with a big group.

At first it was just me, leadership coach Alan Andersen and coach Susan Stringer.  I had never met Susan before and was immediately impressed by her grace, experience and knowledge.  She has a great present and is a very fun conversationalist.  Eventually, more arrived and we kicked off the discussion about "Developing and Managing Human Capital", the first support process in APQC's process classification framework.  The first thing that was made clear is we all agreed that the CAPITAL word in human capital is evil, wrong, etc.  Richard Webb suggested that thinking of people as money is no worst than thinking of them as slaves.  There was agreement on this point.

In search of a starting point, I rattled off the APQC's subtopics:

  • Develop and manage HR planning, policies and strategies
  • Recruit, source and select employees
  • Develop and counsel employees
  • Reward and retain employees
  • Redeploy and retire employees
  • Manage employee information
I told people that I was personally most interested in the "Manage Employee Information" area, where I had the most experience.  It's subtopics are as follows: Manage reporting processes (who reports to whom), Manage employee inquiry process (how management gets info from employees), Manage and maintain employee data, Manage human resource information systems (HRIS), Develop and manage employee metrics, Develop and manage time and attendance systems (we agreed this was an optional step for some places), Manage employee communication.

No one seemed to bite on the above high-level concepts so I started rattling off the discussion topics that we'd covered over the last year: good books we'd read about HR and people-management, alternatives to the resume and is the resume dead, how to get a great job, how to get maximum wages sustainably, what are the current trends and issues, problems in HR management, what does the modern worker like, what do they expect and need, what is the future of employment, what will technology do to HR and management with tools like LinkedIn and CrystalKnows?  Before I could get too far down the list, people locked on the resume topic and we were off on our first big topic.

The resume, truth, recruiting and qualification

Susan gave us some great and interesting facts about millennials in the workforce: that 50% of the workforce will be millennials by 2020 and 75% of the workforce by 2025.  Incredible statistics.  Susan is doing a presentation soon on millennials in the workforce that I will plan to attend.  She is a student of the topic.  I raised issues about complexity dealing with individuals vs. working with people in populations.  Working with 'classes' and things in groups is far easier than but as humans we seem very reluctant to exclusively deal with things in groups and need to give the attention that people and organizations need at an individual level.  

Richard said that the age of authenticity is what's next and was seeking a term for millennials.  I suggested that they were Generation M to keep it simple then we laughed about sequence issues.
We talked about predictive analytics and the power of organizations like Facebook and LinkedIn to predict events from data such as divorce with very high confidence.  Data is a very powerful thing.  
  
I suggested that the resume is just one signal in the collection (stack) of things necessary to understand and work with a person professionally.  Other signals include online profiles like LinkedIn, social media presence, reference checks and the interview.  We didn't believe that the resume would be going away and generrally believed that i was a gateway and door-opener to other aspects of the person.

Susan impressed us with some of her experiences doing hiring at the executive level and gave examples of people she had vetted by requesting 12 references from them: 3 supervisors, 3 peers, 3 suppliers and 3 others.  This sounded very rigorous to me but I could appreciate just how important getting this information really is for some high-risk, high-reward opportunities.

Susan shared that she asks these questions to the candidate, "How would your former managers describe you?" and to the former managers, "How would you describe your former employee?"  They are very open questions and she would listen for incongruity between the stories.  She said she had been referred to by some in the past as "the female version of Columbo", the TV show detective.  What an amazing skill to go this deeply into someone's background not make sure they are who they say they are.

Talent

We got off on a discussion about the quality of leaders and the leadership and it was stated that only A players can hire A players.  Richard told us stories about the Drugstore.com days (joint-venture between Microsoft, Walmart, and some India companies) and how complex and different those cultures were and how they used a 'bus' to communicate effectively.  Another aspect of that collaboration that worked well was to pass information through a key resource they called the seamstress (it was a man) who would bridge the gap and coordinate between the three different teams.  

Books

We talked a little about books here and there and Andrew Sengul regaled us with stories from Aaron Hurst and The Purpose Economy.  The book says that people can be broken up into three categories: those motivated by money, prestige/fame or a deep personal commitment.  The book suggests to only hire the people with deep personal commitment.  Andrew cited quite a few examples of how it is hard to manage and create organizations of these kinds of individuals.

Alan and Susan both highly recommended the book Leadership and Self-Deception.  Alan believes that everyone is a leader (at least sometimes) and they have to start by leading themselves.  

Corruption

Richard is obsessed with the idea that things and people are corrupt.  He believes and here was agreement in the group that one thing we are trying to do with all of these systems and controls in businesses is to weed out corruption, corrupt people and takers.  Richard says that there is a worthy goal to "instrument corruption" (develop systems that can measure and detect corruption at all levels).  Andrew jumped in and offered that experts at corruption really are good at it: that low-grade corruption is easy to detect and that some people really are grade A snakes.  

Steve Kubacki showed up a bit late (but I had already referenced a couple of his ideas) and we talked more about his idea of random firings to weed out corruption and sick cultures.  
Steve says that more of this needs to happen at the top of the organization than the bottom.  Susan said that, "A good leader assesses the talent and weeds out the tenured people."  So her theory is that this can be done by good people but I agree with Steve in some ways that this needs to be done by policy and not just by people (heroes).  We went into a discussion about CEO and he Board and how those two things should work together for control and regulation of the organization.  

Richard wanted to know how to test for integrity.  Everyone agreed that business and corporations really was a battle or war and that more people need to understand that situation.  We went into a discussion about the role of the HR department (few liked it) and Susan gave us examples of HR departments that provided coaching through the "HR Business Partner" who coached the manager of the group.  I have personally witnessed limitations of this model, especially when the management is not ready for coaching.  

"Balancing the bottom line and people" is a big topic that Susan thinks is a key challenge for organizations.  

We went off on a long rabbit trail tangent about sociopaths and predators (evil people) who are ladder climbers.  We tried to separate between those who are sick, ambitious and charismatic.  There is a desire by people to detect and weed these people out.

We talked about the authoritarian personality and how many people are okay with it (even seek it out) and like to live inside of authoritarian structures because they are given something from daddy.  

Conclusions and Next Steps

We had a great turnout.  It was me, leadership coach Alan Andersen, executive coach Susan Stringer, technology architect Richard Webb, professional services pro Lee Carter, delivery operations pro Dena Carter, operations manager Dominic Wong, business owner Thomas Mercer, business leader Thomas Mercer, software product developer Andrew Sengul and creative psychologist Steve Kubacki.

Please join us soon for Episode 8 of the AppsJack Capable Communities Podcast on the HR/Human Capital topic which will feature consulting business owner Aftab Farooqi, coach Rachel Alexandria, psychologist Steven Kubacki, executive and consultant Joe OKonek and professional services sales director Lee Carter.  We will record on Saturday 6/10 and the conversations will be dripped to the major podcast outlets each Sunday morning during June and early July. 

Our next topic for the meetup and podcast will be managing information technology, a topic near and dear to my heart and another key enabler to business.

Tuesday, May 16, 2017

Show Notes - Episode 7 - Managing Customer Service

Recorded: May 13, 2017
Host: Eric Veal
Guests: Ele Munjeli, Michael Cavitt, Andrew Sengul
Legend: Bold = key point

Chat 1 - Strategy

  • Intros
    • EM: devops engineer, JPL contractor, open source org "devopracy" and virtual democracies
    • MC: advisor and organizational consultant, helping leaders think
    • AS: SW dev, interactive narrative
  • EV: Strategy, management, measurement, is customer service dead and why?
  • AS: has it been killed by a new generation of services?  Venmo scams
  • EM: modern online businesses have much less cost. Reputation if bad can be resolved through re-branding.  Businesses more transportable.
  • MC: yellow page ads scams.  Bad service and scams is nothing new.
  • AS: scalability.  people don't scale and there are many humans potentially required.  
  • EM: expectations have changed.  People prefer automated service.  When is it appropriate to have a servant in a democracy?
  • EV: improved skills at delivering service through tech.  
  • EM: do people prefer or trust an ATM more than a teller?
  • EV: strategies can make customer service "dead" by demoting it and not having it be foremost.  Still examples of very high touch services.
  • EV: what was high-touch back in the day is not high-touch now (things change)
  • EM: two channels of people who prefer high touch and people who do not.
  • MC: "how much engagement you want" (depends on the customer).  DIY people vs. people looking to outsource something.  Pricing and services, product mix differs for each audience.
  • EV: markets and populations have people with both types of service needs (high and low).
  • AS: segmentation based on the significance to the buyer.  Segment based on if people see it as significant or not..
  • EV: don't just think about the human interaction part, consider the delivery and automation part other than just the human part.    Human touches diminishing over time?
  • EM: we may be replacing the "real" human interfaces with new human-like interfaces like voice.
  • EV: need to consider the customer service part from the beginning (common mistake).  
  • MC: need to build customer service experience vision into the corporate vision, mission values and long-term strategy.
  • EV: How do we include customer service during our strategic planning?  Looking at failure modes and the dark side?  Possible complaints, issues.
  • MC: need to consider risk and build a "ratchet" so you can go two steps forward but only one step back, for example (build in quality).  "The Luck Factor".  Write scenarios for the business.
  • EM: repair-driven systems design.  Program around areas where you know you'll have problems.  Build tools as you build products (comprehensive).
  • AS: Picture the failure from the eyes of the customer and design / build /release accordingly?
  • EM: Uber having issues now.  Transparent remediation.  
  • MC: Need things pre-emptively and to consider beforehand so we are more prepared?
  • AS: Humans encouraged to remove themselves from the sphere of customer interaction over time? 
  • EM: how do you build trust in automation? 
  • MC: customers really don't care, they just want their outcome.

Chat 2 - Managing customer service operations

  • EV: workforce, requests, and complaints
  • MC: Geico experience.  Sales and service tightly coupled.  Goal to resolve quickly with as few calls as possible.  People managed to reduce time on the phone.  Policies created conflicts.  You get what you measure in a lot of ways.
  • EM: Geico very pro-automation.  They have a non-human representative.  "Golden age of phone service".  More companies doing voice-to-text analysis.
  • MC: Hiring problem: no easy way to tell if a person is going to be good in customer service until you hear someone on the phone or see them in front of a customer.  
  • AS: Business and HR likes rote checklists
  • EM: wants more analysis on exceptional customer service.  What does it look like?  Predictive and anticipatory.  Are the best ones teachers?
  • EV: Skill required at many levels and a lot of risk.
  • AS: Human Competence book link.  People get stuck in 'cargo cults' who build a culture around checklists but have no agility, creativity or out-of-the-box thinking. What is the desired result?
  • EM: Humor plays an important role of moving from business-only to personal / deeper relationship.  
  • AS: The "Cute-ify-ing" of authority.
  • EM: Citizenship and extending government services.  Can't force adoption.  
  • EV: The weight of service delivery can be a lot when you are a consultant.  Working as a team way better, reduces the risk.
  • EM: Great delivery comes from empowerment.  Career "pathing" makes a difference.   What paths are available for people that start as customer service?
  • EV: People who start in the field can wind up in powerful positions.  But is this a common path?  Methods: 1) revolving door 2) isolated service org 3) one where people go to other departments.
  • AS: Institutions act primarily to further their own existence.
  • MC: Going from line / delivery into managerial roles is not necessarily good.  Army did specialist ranks.  Managerial routes don't always make sense.
  • EM: Tech support should get into UX at some point.  Need a closed loop.  Tech support part of the design process, instrumental in designing the requirements, for example.  50% of problems are usability problems.  

Chat 3 - Measuring customer service

  • AS: Cargo cults further explained.  Tribes would keep hoping for the planes would keep coming.  Doing non-value adding things and hoping.  Opportunity to find low performers and bring them up (low hanging fruit).  Need to set priorities and focus.
  • EM: What and how are you measuring success and failure.  What is a meaningful failure?  Some people rewarding the wrong things and behaviors (like people fixing bad issues)...as it encourages more bad behavior in the future.
  • MC: Celebrate the architects or the recovery team?  Information overload can be bad.  Not good to just get all the info.  Know the questions.
  • EM: Designing good metrics is a trick.  Need to avoid bias and ask good questions (need good science).  There's a wrong way to ask questions and gather info.  Witch hunts, for examples, not a great way to gather info or do science.
  • AS: Absurd metric examples.  "How slurred is their voice?"
  • EV: Instrumentation and telemetry a big part of this (more is good) but still need filters and need to roll it up, prioritize, control, etc.  But more data generally a good thing.
  • MC: Text-to-speech analysis is important and good feedback source.  Changes many things.
  • EM: The relationship and rapport allows us to get better data.  Have users participate in the process.
  • EV: Cost of getting feedback reducing through better instrumented products.  Doesn't require customers to actively give feedback but do through use instead.  Build the feedback system right into the product like a vacuum could detect it being kicked or sworn at.
  • EM: Want a closed feedback loop where the feedback you gave was finally told to you that your comment mattered, when and how.  
  • AS: Investment and significance.  
  • EV: Investment happens on both sides: the customer and the provider.  Both need to be invested and quid pro quo may be needed.
  • AS: Speculation and investment.  A financial question.
  • EV: Human capital is next.

Sunday, April 2, 2017

AppsJack Capable Communities Meetup – March 2017 – Delivering Product & Services Discussion

Tuesday, March 28, 2017 4 PM
Kirkland, WA


A few business associates and I gathered last Tuesday to talk about challenges relating to delivering products & services.  Delivering products and services is the fourth element in the APQC model.  I showed up at about 3:30 and struck up a conversation with Alan Andersen who was already there.  Alan is a leadership coach and consultant.

I’ve been fortunate to get to know Alan better over the last couple of months and it’s been a good experience for me.  Alan is well read and has so many experiences working with leaders and teams from which he can draw experiences and stories.  We sat and chatted and then a few more people showed up at our table, the Captain's Table.

Richard Webb, always a powerful and interesting force, showed up and we started to get into the meat of the delivery topic.  James Tuff, an entertaining and vivacious technology sales executive and entrepreneur, showed up and sat at the head of the table.  After long we had eight at the table including clinical psychologist and writer Steve Kubacki, an intelligent, insightful, opinionated professional and mountaineer.  Steve is great at these events in that he helps us stayed grounded, balanced and on point.  Steve regularly shares perspectives that help us see things from a more human, less business, perspective.  Tonight was no exception.

My new friend, Thomas Mercer, was sitting to my right.  I was drinking iced tea in copious amounts; I had been sick with a fever earlier in the week but was starting to spring back to life.  Spring was upon us indeed.  12 years prior, Thomas and I had finished the same master’s program at the University of Washington Foster Business School: information systems where we learned about the internet, networks, business.  And when things like Facebook were brand new.  Thomas previously ran a medical practice business that helped people with irritable bowel syndrome with diagnosis and treatment.  He explained to us his time working on that project and ho it related to the challenges of delivery.

Lee Carter, sitting to my left, is a business development manager for Ciber, a technology consulting firm with some major clients in the area, recently relocated to the Seattle area from Dallas, TX.  We were also graced by Bruce Follansbee’s presence.  Bruce is always good for conversation, putting people at ease, and book references.

One of the first things I asked about was blockchain and its relationship to delivery.  Per wikipedia:
blockchain is a distributed database that maintains a continuously growing list of ordered records called blocks. Each block contains a timestamp and a link to a previous block.[6] By design, blockchains are inherently resistant to modification of the data — once recorded, the data in a block cannot be altered retroactively. Through the use of a peer-to-peer network and a distributed timestamping server, a blockchain database is managed autonomously. Blockchains are "an open, distributed ledger that can record transactions between two parties efficiently and in a verifiable and permanent way. The ledger itself can also be programmed to trigger transactions automatically."
Richard and Thomas seemed to know quite a bit on the subject and shared what they knew with us.  There was discussion about whether the blockchains should be open or closed, transparent or not.  Issues related to security and privacy were major pivot points for our discussion.  Richard suggested that we loop in Ellen Mooney into the conversation; I guess she is an expert on the topic of digital democracy.

We were pretty much all over the map in the beginning of the discussion, going from micro levels of delivery (firm or product perspectives) up to the macro levels (global supply chains, politics and economics).  Richard talked about Amazon’s CIDC pipelines and brought up the term “logistics engine”.  Many at the table agreed that Amazon is doing very amazing things these days and that their ability to delivery and run supply chains is amazing.  For many years, Walmart, the world’s largest company by revenue in the world, has been known for its logistics and methods like “cross-docking” but it seems that Amazon, between its online presence and many innovative new products and services has begun to eat into that area of innovation.  Much is happening with Amazon.

We talked about hypothetical scenarios where Amazon could, for example, run dentist offices and use 3d printing for delivery of replacement teeth.  It didn’t seem very far-fetched.  Richard mentioned and recommended the movie Elysium which has some interesting and futuristic elements to it where people get scanned with lasers and good things happen.

I realized at some point in the bubbling conversation that the differences between delivering services and delivering products really are stark.  APQC has even recognized this issue by breaking them out into different L1 elements, making the model 13 items, no longer 12.  I think it’s important to pick one or the other for the sake of focus, clarity and conversation.  Delivering products seems a bit easier in that they are tangible and “real”, whereas delivering services seems a bit more human and ambiguous and challenging, at least to me.  Richard doesn't believe that the distinction is all that different.  Similarities between delivering services and managing customer service (the next area in the AQPC model) seem obvious and will be the target of future exploration.

We got into a pretty detailed conversation about banking, the flow of money, financial systems and corruption.  Richard is very passionate about the many issues of corruption and it helps to have Steve there for his thoughts on humanity as well.  Richard gave examples of Visa being able to run all transactions in the world on its system alone.  Steve made some interesting points about capitalism, such as:
“Capitalism is about wiping out the competition as much as possible so you can waste as much as you want.”  
Steve’s a funny guy and I don’t disagree with the point.  I know some people who definitely act that way.  For these people I know, the goal is to get really rich and make a lot of money now so they can chill out, retire and do very little later.  They aren’t trying to create economies or markets or anything, they are trying to dominate existing ones.  In a word: take.  Not my kind of verb.

Someone mentioned the book by Chris Anderson “Free: The Future of a Radical Price” and cited that it was interesting.  James Tuff shared about a new business idea he is working on in the transportation and informatics areas and we all found it interesting helping him think about how he could deliver that set of products and services.  We had a lengthy and fruitful conversation with Reba about her challenges and ideas for competing and delivering value in the very rapidly changing real estate industry.

Business is highly complex and so is delivery.  Delivery is where the rubber meets the road.  Analyzing any business from the perspective of delivery is difficult because of the natural complexity.

Stay tuned for the upcoming podcast episode on delivery when I will sit down with Josh Bosworth and Steve Kubacki to bat the topic around.


Friday, January 27, 2017

26 Interesting Things About Modern Product & Service Development

We are prepping for the February Podcast, which will be about Developing & Managing Products and Services.  It's an exciting and fun topics.  Here are some of the highlights from the meetup that we are considering for the Podcast.  Please provide your input and ideas or what you would like us to cover.  What challenges do you have with the topic?  What blind spots are there?  What practices and principles have you used that worked?


  1. Chaos Theory and Non-Linear Dynamics
  2. The Developing and Managing Products and Services area from the APQC PCF (link
  3. Known small effects that have lead to huge changes, issues, problems, catastrophes or events: the butterfly effect, the straw that broke the camel's back and other tipping points. 1 degree shifts.
  4. What are elements, tools and practices of the modern practice of product and service development?
    1. In Software
    2. Physical Products
    3. Services
  5. Which companies are making the best and most innovative products today and how?  Why?  For example, the DJI Mavic Drones, South Park, Air BnB, Uber, who else?
  6. Who is providing the best service today and how?  What are the elements of it?
  7. The importance of decision making and how differences in beliefs or decisions can grossly impact the quality of success on a project.
  8. "Incantations" and parrots.  How many people are simply repeating others and not questioning the cause or underlying assumptions that fed into what they currently see or perceive?  Copy cats might not and should not last. (Developing the deepest and most defensible niche).
  9. The topic of "Everything dies or is dying"
  10. Application and Product Lifecycle Management, Phases of Product Lifecycles (Plan, Define, Realize, Commericalize, Phase Out) and it also includes Supply Chain Managmeent and Customer Relationship Management (And SUpport Processes)
  11. Is PLM the core engine of value and growth within a company (probably)?
  12. Techniques for being able to reasonably work with complexity or complex systems, ideas, concepts, etc.
  13. What are the problems and challenges in working with complex systems?  What are the tools for overcoming their challenges?
  14. Attribution: how it might be hard to determine what really was the original impact, actor, etc. that caused a process to develop into what it is today or what it would / could become.
  15. Why did "non-linear management" get so many eye-rolls when shared with the group?  Isn't that what we're talking about after all?  Too much of a buzzword?
  16. Challenges with "insight alignment" and how we can have and align group insights for optimal performance, value and outcomes.
  17. Entropy and counter-entropy systems.  Organizing around an increasingly chaotic world.
  18. "An organizational immune system" and what it would be.  What are its properties and methods?  
  19. Product intelligence vs. business intelligence.  Is one bottoms up and the other tops down?  Do both matter?
  20. Thresholds and control systems, alerts and alarms for responding to important conditions
  21. The need for "crossing domains" for innovation and creativity.  Yin and Yang as opposing forces that somehow find balance in the middle.  If the world could be seen as these components, what would they be and how would they be managed?
  22. Which metrics matter and how would we identify missing metrics in our model before it was too late?
  23. Divine flaws, fractures, and "seeds of disaster".  Are they really there?  Does this feature really exist in everything?
  24. The need to "go up one level of abstraction" and to use data, models and visualization for managing.
  25. Failing fast and failing slow.  Combating the forces of failure and death in business.
  26. Two separate forces in innovation 1) truly producing something new and out of context 2) integrating that product/service/thing into an existing company, product line, market, etc.  What do we call these practices?
Tune into Episode 4 of the AppsJack Capable Communities Podcast in mid February '17 to hear more about all of these topics.

Wednesday, December 21, 2016

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?