Slide 1

Slide 1 text

Speaking Client:
 Explaining Technical Stuff to
 Non-Technical People Introduction to Communication Skills,
 the Project Lifecycle & Scope Creep

Slide 2

Slide 2 text

Jim True Support Lead & Community Manager
 Pods Framework http://pods.io | @podsframework http://jimtrue.com | @jimtrue

Slide 3

Slide 3 text

We start our story in Space, with some aliens zipping around the galaxy…

Slide 4

Slide 4 text

Suddenly, they have an issue with their
 organic hydroponic hyperdrive engine…

Slide 5

Slide 5 text

Luckily, they’re in the vicinity of the Milky Way Galaxy…

Slide 6

Slide 6 text

They decide to drop in on the Earth to see if they can find any intelligent species to help

Slide 7

Slide 7 text

They decide to start their search in the North American province, the Nation’s Capitol, Washington DC

Slide 8

Slide 8 text

NO INTELLIGENT
 LIFEFORMS! Obviously, no luck there.

Slide 9

Slide 9 text

SUCCESS!
 INTELLIGENCE!! Checking social media, they read about this amazing Tech School in St Petersburg, The Iron Yard

Slide 10

Slide 10 text

They drop in and meet the locals

Slide 11

Slide 11 text

They drop in and meet the locals

Slide 12

Slide 12 text

Greetings Earthling! Our Organic Hydroponic Hyperdrive Engine is damaged. Can you help us fix it?

Slide 13

Slide 13 text

Be Happy To, but I’m teaching a class on Talking Tech Stuff to Non-Tech People. Think you can assist me?

Slide 14

Slide 14 text

YES! We’d love to! 
 Growing a new engine will take a month minimum.
 Let’s start by cleaning up this “screen clutter”

Slide 15

Slide 15 text

The COMMUNICATION
 Toolkit • Context • Empathy / Perspective • Common Ground • Comparisons & Analogies • Clarify by Asking Questions

Slide 16

Slide 16 text

Context Matters! Does this mean what I think it means? And it can mean different things depending on the ‘context’ in which I’m using them.

Slide 17

Slide 17 text

Perspective & Empathy You can’t know how hard something is until you walk a mile in someone else’s shoes. You also can’t explain something if you don’t try to see it from their perspective.

Slide 18

Slide 18 text

Common Ground Speak at the SAME Level Don’t speak down to someone (insults their intelligence or ability to understand) & Don’t Speak over their heads. Avoid Jargon, Acronyms and words that have multiple meanings (context!)

Slide 19

Slide 19 text

Make Comparisons with Analogy It’s much easier to explain something if you can give someone a more common frame of reference that ‘works’ the same way. Find analogies with your audience/client and use them!

Slide 20

Slide 20 text

Clarify by Asking Questions Ask the person, often, if they’re following what you’re explaining or providing what you expect. Have them explain the problem back to you, so you can clarify they understood what you communicated.

Slide 21

Slide 21 text

The PROJECT Lifecycle Everything that takes time to complete is a Project. Anything you want to manage, has these same steps:
 ‣ Discovery ‣ Design ‣ Develop ‣ Delivery ‣ Deploy

Slide 22

Slide 22 text

DISCOVERY “Is what you say you want what you really want and do you know what I mean when I say what I want?” DEFINE what the project is expected to accomplish. Build Requirements, create the DEFINITION of the project.

Slide 23

Slide 23 text

DESIGN Make a mockup, a drawing, a demo, or something that doesn’t take too much effort to give a visual/sensory/tangible representation of what the client wants. Can be called the REFINE stage, because changes help clarify the DEFINITION.

Slide 24

Slide 24 text

DEVELOP Put all the time and effort in Discovery and Design to actually CREATE what the project requires. Also known as the BUILD phase, because at this point, you can’t go back without destroying.

Slide 25

Slide 25 text

DELIVERY Provide the finished project to the client in a way that they can ‘test’ and ‘kick the tires’. Project can be tested, investigated for “little” changes/fixes/bugs. Client will make a list of changes from actually using the product. This is the PUNCH LIST.

Slide 26

Slide 26 text

DEPLOY “Putting the baby out into the world and seeing if it floats.” This is also, usually, when ownership changes hands of the project to the requestor.

Slide 27

Slide 27 text

MILESTONES DISCOVERY DESIGN DEVELOP DELIVER $ $ $ $ Important Steps/Stages in
 Project Lifecycle Milestone Dates Payments Due

Slide 28

Slide 28 text

SCOPE CREEP DISCOVERY DESIGN DEVELOP DELIVER Changes Occurring DURING the
 Project Lifecycle Scope Danger

Slide 29

Slide 29 text

SCOPE CREEP DESIGN DEVELOP DELIVER Changes in Scope made After Discovery, mean the project may have to jump back to the prior milestone or Start Over from scratch.

Slide 30

Slide 30 text

SCOPE CREEP DESIGN DEVELOP DELIVER Costs MUCH more MONEY to make changes the closer to the end of the project as well. $ $ $ $ $ $ $ $ $ $ $ $ $

Slide 31

Slide 31 text

DISCOVERY is CRITICAL This is why you spend the necessary time in the Discovery Phase. It will always cost more resources & time to change a project after it leaves Discovery.

Slide 32

Slide 32 text

Speaking of Discovery The book "Start With The Why" outlines how you achieve more by focusing on the underlying reasons why people do what they do. In WordPress development discovery, using the principles outlined in the book, we can turn a small request into a much larger one by figuring out the business problems associated with the request, and proposing a larger solution which resolves the underlying problems. “Start with the Why, Leave with a Bigger Check” Thursday, June 1, @ 6:30pm
 Iron Yard, St Pete

Slide 33

Slide 33 text

Questions?

Slide 34

Slide 34 text

Jim True Support Lead & Community Manager
 Pods Framework http://pods.io | @podsframework http://jimtrue.com | @jimtrue

Slide 35

Slide 35 text

Tampa Bay WordPress Meetups Monthly in St Pete @ Iron Yard
 1st Thursdays every Month http://tampabaywp.org | @tampabaywp Slack Chat | Facebook Group | Meetup