Thursday, April 20, 2017

Episode 6 - Business Skill 4 - Deliver - Part 1


Show Notes for AppsJack Podcast Episode 6 - Delivering Products and Services

We had a great conversation with some seriously smart and educated peeps about the future of product & service delivery, differences between products and services, virtual reality, robotics, human needs and work.  Listen soon!

  • Topic: Delivering Products and Services
  • Recorded 4/15/17 in West Seattle, WA
  • Guests: Josh Bosworth, Steve Kubacki, Ele Munjeli, Andrew Sengul

SECTION 1 - DEFINITIONS AND EXAMPLES - DIFFERENCES AND COMMONALITIES BETWEEN DELIVERING PRODUCTS & SERVICES - DIFFERENCES BETWEEN WHAT MAKES A PRODUCT AND SERVICE THEMSELVES

  • Eli
    • Beyond staff augmentation
    • Bundling services into a product
    • Services as they interact are discreet
    • Better to think of services as products
    • Can't / don't want to sell "golden handcuffs"
    • "Productized services"
    • Product is the mature interface of the service
    • Cloud is / was abstract and nebulous but truly is concrete and needs to be
    • Virtues of productizing services
    • Have a set price for the service is a key maturity step
    • Continuing to abstract and simplify
    • Mass customization as a goal for infrastructure
    • "Nobody misses the cashiers."
    • We don't idealize servants (people in services) because of democracy.
  • Andrew
    • Toil is linear work that doesn't scale
    • Can toil be eliminated?
  • Josh
    • Do services necessarily have humans involved?
    • Shovel example
    • Shovel ordering today - digitally
    • Old ways of getting shovels
    • Outcomes of services
  • Eric
    • Product as a metaphor for maturity
 

SECTION 2 - THE IDEAL ROLE FOR HUMANS IN OUR BUSINESS AND WORK PROCESSES - FUNCTIONS TO RESERVE FOR HUMANS - WHAT WE SHOULD NOT AUTOMATE - ETHICS

  • Josh
    • The power of human massage and touch. Irreplaceable?
    • Analysis as part of the sales/delivery process seems to still be appreciated.
    • User reviews the "analog" of storytelling in the digital domain.
  • Eric
    • Ripple effects caused by small human interactions.
    • The idea of 'displacement' when people are no longer needed in systems/processes/supply chains.
    • Need to think systematically to plan to pick up the waste and displacement (delta) from a previous change. This has always been a thing.
  • Ele
    • Differences between "good service" and just plain service.
    • We don't like to see servants (people in service/delivery processes).
    • "The new paradigm of work."
    • Now mass customization, not mass production.
  • Steve
    • The importance of human touch for human development.
    • Need to create and reserve social connectedness.
    • Nature is unique and unpredictable, dynamic.
    • Humans have a draw to uniqueness.
    • Surgical outcomes are dramatically better if the doctor spends time talking to the patient.
    • Not all occupations suit everyone.
  • Andrew
    • Many automated processes lack storytelling.
    • New economy and new job variety is very limited.
 

Section 3 - The future, the fidelity of virtual reality and the built world

  • Andrew
    • The empathy box.
    • Journey the game.
    • A VR world for politicians who love fame but do it safely and virtually.
  • Eric
    • Help the politicians by helping them get out of the way.
    • 5 Senses and fidelity: just how complete is the virtual thing?
  • Josh
    • Experiences with VR.
    • Desire to see loved ones in VR space.
    • The VR hardware store and associate.
  • Steve
    • The power of imagination.
    • We're kind of doing virtual reality in our minds.
    • VR and religion.
    • What do we want to practice in VR?
    • Directly vote through our machines to make decisions.
    • Make the world more diplomatic.
  • Ele
    • The human brain is kind of digital (neurons fire on and off).
    • VR is a matter of fidelity.
    • Dreams are a virtual experience.
    • Use of VR in Taiwan to build empathy between people.
    • VR to extend our humanity.
    • VR to "visit your mother" and other loved ones.
    • Politicians should be open source robots.
    • VR as a place to be safely deviant.
 

SECTION 4 - THE FUTURE OF WORK, EMPLOYMENT, TOIL AND COERCIVE SITUATIONS - IDEAL JOBS - PROS AND CONS OF AUTOMATION

  • Eric
    • The coin of automation. What is it?
  • Ele
    • Automation as liberation technology; eliminating toil.
    • Automation is your super power.
    • Delegation is a kind of automation.
    • Need to teach automation, its pros and cons.
    • Automation as a spiritual practice. Recognize toil when you come across it. Design and decision-making / project management issue.
    • A personal journey to automate all of our own toil away.
    • Craft is not toil.
  • Steve
    • Automation is not necessarily a good thing.
    • Automation creating more and more poor people.
    • The way we're dealing with automation is not working.
    • Does automation always create greater choice for the employee?
    • When things are automated, who are the beneficiaries (goes up to the top and to the automaters).
    • People need merit, accountability, decision-making so it is not toil.
    • Job, work environment and mindset all have an impact on what is toil and gives meaning.
  • Andrew
    • Toil and non-toil tasks.
    • The cost of non-toil tasks.
  • Josh
    • Toil very subjective and situational. Hard to generalize about it.

 


Check out this episode!

Monday, April 17, 2017

Show Notes for AppsJack Podcast Episode 6 - Delivering Products and Services

We had a great conversation with some seriously smart and educated peeps about the future of product & service delivery, differences between products and services, virtual reality, robotics, human needs and work.  Listen soon!

  • Topic: Delivering Products and Services
  • Recorded 4/15/17 in West Seattle, WA
  • Guests: Josh Bosworth, Steve Kubacki, Ele Munjeli, Andrew Sengul


Section 1 - Definitions and Examples - Differences and commonalities between delivering products & services - Differences between what makes a product and service themselves

  • Eli
    • Beyond staff augmentation
    • Bundling services into a product
    • Services as they interact are discreet
    • Better to think of services as products
    • Can't / don't want to sell "golden handcuffs"
    • "Productized services"
    • Product is the mature interface of the service
    • Cloud is / was abstract and nebulous but truly is concrete and needs to be
    • Virtues of productizing services
    • Have a set price for the service is a key maturity step
    • Continuing to abstract and simplify
    • Mass customization as a goal for infrastructure
    • "Nobody misses the cashiers."
    • We don't idealize servants (people in services) because of democracy.
  • Andrew
    • Toil is linear work that doesn't scale
    • Can toil be eliminated?
  • Josh
    • Do services necessarily have humans involved?
    • Shovel example
    • Shovel ordering today - digitally
    • Old ways of getting shovels
    • Outcomes of services
  • Eric
    • Product as a metaphor for maturity

Section 2 - The ideal role for humans in our business and work processes - Functions to reserve for humans - what we should not automate - ethics

  • Josh
    • The power of human massage and touch. Irreplaceable?
    • Analysis as part of the sales/delivery process seems to still be appreciated.
    • User reviews the "analog" of storytelling in the digital domain.
  • Eric
    • Ripple effects caused by small human interactions.
    • The idea of 'displacement' when people are no longer needed in systems/processes/supply chains.
    • Need to think systematically to plan to pick up the waste and displacement (delta) from a previous change. This has always been a thing.
  • Ele
    • Differences between "good service" and just plain service.
    • We don't like to see servants (people in service/delivery processes).
    • "The new paradigm of work."
    • Now mass customization, not mass production.
  • Steve
    • The importance of human touch for human development.
    • Need to create and reserve social connectedness.
    • Nature is unique and unpredictable, dynamic.
    • Humans have a draw to uniqueness.
    • Surgical outcomes are dramatically better if the doctor spends time talking to the patient.
    • Not all occupations suit everyone.
  • Andrew
    • Many automated processes lack storytelling.
    • New economy and new job variety is very limited.

Section 3 - The future, the fidelity of virtual reality and the built world

  • Andrew
    • The empathy box.
    • Journey the game.
    • A VR world for politicians who love fame but do it safely and virtually.
  • Eric
    • Help the politicians by helping them get out of the way.
    • 5 Senses and fidelity: just how complete is the virtual thing?
  • Josh
    • Experiences with VR.
    • Desire to see loved ones in VR space.
    • The VR hardware store and associate.
  • Steve
    • The power of imagination.
    • We're kind of doing virtual reality in our minds.
    • VR and religion.
    • What do we want to practice in VR?
    • Directly vote through our machines to make decisions.
    • Make the world more diplomatic.
  • Ele
    • The human brain is kind of digital (neurons fire on and off).
    • VR is a matter of fidelity.
    • Dreams are a virtual experience.
    • Use of VR in Taiwan to build empathy between people.
    • VR to extend our humanity.
    • VR to "visit your mother" and other loved ones.
    • Politicians should be open source robots.
    • VR as a place to be safely deviant.

Section 4 - The future of work, employment, toil and coercive situations - ideal jobs - pros and cons of automation

  • Eric
    • The coin of automation. What is it?
  • Ele
    • Automation as liberation technology; eliminating toil.
    • Automation is your super power.
    • Delegation is a kind of automation.
    • Need to teach automation, its pros and cons.
    • Automation as a spiritual practice. Recognize toil when you come across it. Design and decision-making / project management issue.
    • A personal journey to automate all of our own toil away.
    • Craft is not toil.
  • Steve
    • Automation is not necessarily a good thing.
    • Automation creating more and more poor people.
    • The way we're dealing with automation is not working.
    • Does automation always create greater choice for the employee?
    • When things are automated, who are the beneficiaries (goes up to the top and to the automaters).
    • People need merit, accountability, decision-making so it is not toil.
    • Job, work environment and mindset all have an impact on what is toil and gives meaning.
  • Andrew
    • Toil and non-toil tasks.
    • The cost of non-toil tasks.
  • Josh
    • Toil very subjective and situational. Hard to generalize about it.

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.