Why I will focus more on the human in the future of industrie & living

In the last years and month I kept my eye on the areas of Industrie 4.0 or Industrial Internet. While I will continue this journey, and will refocus more on the area around lifestyle and healthcare and consumer products. Why?

I definitely believe that there is large potential in Industrie 4.0, I personally am quite surprised with the experience how long it takes until an idea makes it to pilot or even production in the enterprise it. In the consumer area the cycle times are much lower.

But there are two more important reasons. First I enjoy helping people, and when I thought about my dream when I was a little boy, I dreamed to help people make the world a better place by making them more happy and helping them to be healthy. Well back then I dream of healing every diseases and fixing all the world problems form climate change to mass hunger. Most likely this will stay a dream, but I love the idea to contribute a small small piece to something meaningful.

I always believe I could do something meaningful, and this does not mean to revolutionise the world, only few of us are luck enough to experience this. But do something meaningful means to putting your head to a meaningful challenge and throwing punches to wear down the challenge for a heavy hitter to punch it out.

But do something meaningful means to putting your head to a meaningful challenge and throwing punches to wear down the challenge for a heavy hitter to punch it out.

So we come to the third reason: I am currently working at IBM, and one reasons I chose to work for IBM was that they brand themselves as a company that contributes something meaningful the the solutions of large problems. Currently I integrate systems at big banks, while this is important, it seams quite meaningless compared to curing cancer or alzheimer’s or any other disease. But as it seems we IBM has not given up on making meaningful contributions. When they announced in April 2015 that “healthcare will be our moonshot”, I knew that I have to be a part of this. Therefore I will refocus on this area, and learn what is important about this topic and how it can be combined with the Internet of Things. I see a large overlap between Industrie 4.0 and the consumer side. I think we will get a much larger acceptance for Industrie 4.0 to be not just another buzzword, when we focus on the customer and identify areas where we can generate immediate benefit to the people.

What this will mean for my focus areas, well I will have to keep learning to develop and maintain apps on a cloud platform. This includes connecting things to the cloud with Arduino & Node.JS. Those Applications will follow a modern agile Microservice architecture. But modern application need also some analytics to generate value from data. To do this I will useApache Spark, Java, Python, R and Statistics.

This will be continued!

Monthly review: November 2014

In November I spend most of my time learning how to use the IBM Integration Bus SAP Adapter and File Adapter. Also I am glade to took the time to change my diet. I packed 20 kg in the last 2 years. And I have to loose those. Also I invested some time in networking and building up my twitter audience. This allows me to share information much more effectively.

Especially I talk to Matthias Günther about Industrie 4.0 projects. And we agreed that there is a large potential for a cloud based IoT Analytics solution. And we agreed to keep in touch about the topic. So if you are interested in joining the project mail me.

For Dezember I plan to:

workx:

  • Installing the IBM Integration Bus SAP Adapter 
  • Connecting to SAP via RFC/BAPI Outbound and Inbound 
  • Connecting to SAP via ALE/iDoc Outbound and Inbound 
  • Modelling Binary Data (a SAP iDoc) with DFDL) 
  • Using the IBM Integration Bus File Adapter 
  • Configuring the IBM Integration Bus SAP Adapter Security using SAP SNC
  • Learing ESQL for IBM Integration Bus 
 
  • Wireframing a Mobile Application with Sketch 3
  • Bootstrap the mobile application development with Yoman scuffolding for Ionic and AngularJS
  • Using Bluemix Mobile Cloud Services with a hybrid cordova app
  • Implement a Bluemix Push Notification
  • Compile mobile app and publish in App Stores 

personalx:

Meeting Process

SHORT SUMMARY:

  • Location: Yelp: 3.5 or more stars, $-$$, noise level: average or quiet, accepts credit cards, wifi: free (if possible), accepts reservations if possible. (Make reservations under “Dennis Seidel”)
  • Please create “Travel” appointments 1h before and 2h after lunches and 1h before / 1h after coffee.
  • Make sure calendar entries have location and backup contact info.
  • Cc: me on all correspondence. If you need action/input from me, add @Dennis: <message> near the top of the e-mail.
DETAILS

I think it is awesome to get to easily set lunches, coffees, and calls with people. This is how that process looks like:

  1. I bump into people in person or get an email from them. If I meet them in person, I scan in or take a picture of their business card and add it to my file.
  2. I introduce myself via e-mail and ask him/her to schedule lunch/coffee/a call. I use an e-mail template on my computer or a snippet on my phone to make sure that I include all the information necessary. I also refers to a note with my preferences and processes.
  3. I contacts the person and negotiates schedule / location using http://doodle.com/dennisseidel or manual scheduling through e-mail, following up in case people don’t respond. If possible, we’ll suggest a venue with good WiFi near the person’s office or location. He or she would create a calendar entry for the meeting as well as travel/preparation time around it.
  4. We have a task board where I could see where people are in the process, so I can be sure that nothing slips through the cracks  and we review it periodically.

It’s important to me that the process doesn’t make people feel like I’m standoffish or self-important. I also want to make sure that we don’t drop the ball even if I take tasks back, so I want to use something like Trello to track scheduling status.

PROCESS

STEP 1. Find a time that works for people.

In Stuttgart? Offer lunch or coffee/tea, my treat. I prefer 60 minutes for lunch or coffee/tea, and 30 minutes for a phone call. I’ll take 30 minutes for coffee/tea if needed.
Days: I prefer to meet on Monday or Friday, usually afternoons. Ask me before offering mornings or anything that conflicts with something else on my calendar.
Buffer time: Around lunch appointments, I prefer to have at least 1 hour free before lunch and 2 hours free after (-1h/+2h). For coffee, I prefer to have 1 hour free before and 1 hour free after (-1h/+1h). Please create “Travel” appointments blocking off the time once the time is confirmed.
Suggest three times on different dates. In the same email, ask them to check http://doodle.com/dennisseidel for other times if the times don’t work. If meeting them in person, ask them where they’ll be on that day.

Check my address book to see if I have a cellphone number for them. If not, ask them for a cellphone number I can reach them at just in case something comes up, and add that to their address book entry. You can use http://contacts.linkedin.com to update contacts in my address book.

Negotiate time if needed. If they respond by email, check that the times still work with my schedule, create calendar entries, and invite them.

STEP 2: SUGGEST A LOCATION

If they suggest a place, go with their suggestion.

If they don’t suggest a specific place, just a neighbourhood or intersection, use yelp.ca and suggest something (or see my preferences below). Criteria for Yelp: 3.5 or more stars, $-$$, noise level: average or quiet, accepts credit cards, wifi: free (if possible), accepts reservations if possible. If the place accepts reservations, please reserve – pick a different place if you can’t get a reservation on that date.

If they don’t suggest a location, or they want us to suggest:

Coffee:

  • Monday: […]
  • Friday: […]
  • Reutlingen Downtown: Alexandre
  • Ehningen IBM:
  • Stuttgart Downtown: […]

Lunch:

  • Reutlingen Downtown:
  • Ehningen IBM:
  • Stuttgart Downtown: […]

STEP 3: CREATE CALENDAR ENTRY, OR UPDATE IT IF SCHEDULEONCE HAS CREATED ONE (I’ll forward you the e-mails)

Add to Google Calendar: Dennis / Hard Appointments

Title: Person’s name – Dennis Seidel: Discuss <topic>

Location: Name of restaurant, address

Attendees: invite them

Description:

Dennis Seidel’s cellphone: 0171 1277440

Link to Yelp page for restaurant

<agenda or body of email>

(Happy to reschedule or move – introduce me to your favourite place!)

If the place accepts reservations, please call and make them under the name “Dennis Seidel”, and add a note to the calendar entry.

STEP 4. FOLLOW UP

Check the calendar entry two business days before the event. Follow up with email confirming the date and time, asking them to edit the calendar entry or email me at mail@dennisseidel.de if they need to reschedule.

TEMPLATES

Sample e-mail introducing the assistant and asking her to set things up

Hello, John!

I’d love to meet with you for lunch to discuss sketchnoting – my treat. Could you please organize lunch for maybe the second week of December? Thank you!

Dennis Seidel

Sample e-mail from assistant

Hello, John!

For lunch, would either Dec 10 (Mon), Dec 11 (Tue), or Dec 13 (Thu) work for you? 12pm usually works, but she’s happy to meet earlier or later if needed. Alternatively, if none of those dates work for you, you can check her availability at http://doodle.com/dennisseidel or send me a few dates and times that fit your schedule.

Also, where will you be at that time? If you’ll be near your office at 123 Anywhere Street, I can find a restaurant nearby. If you’ll be elsewhere, tell me and I’ll look for somewhere close – anywhere near the subway line would be fantastic. Got a favourite? We’d love to find out about it!

What phone number would be the best to reach you at in case something comes up?

Best regards,

Dennis Seidel

Sample calendar entry

Subject: Lunch: John / Dennis – sketchnotes

Attendees: john@example.com

Location: Restaurant Name (123 Restaurant Address St., Toronto)

Sacha’s phone: 416-823-2669

Your phone: 123-456-7890

Restaurant website: http://www.example.com

On Yelp: http://www.example.com

To reschedule, please contact me at ______ . Need to reschedule on the day of the event? Please call Dennis.

 

 

<agenda / notes from e-mail>

Sample confirmation

Hello, John!

This is Dennis again. I’ve set up the calendar invitation for your meeting with me for 12pm on Dec 13 at Restaurant Name. Please tell me if you’re having problems adding it to your calendar. If you need to reschedule, please feel free to get in touch with me. You can check http://doodle.com/dennisseidel for updated availability. If you’re rescheduling on the same day, please call me at 0171 1277440. Thank you, and I hope you have a great conversation!

Dennis Seidel

todo workflow

The todo process is based on agile principles (you find them below) and the goal of my todo process is to facilitate three things:

  • to PLAN: I get an overview of all potential todos and break them down into 25 minutes tasks
  • to PRIORITIZE: I make sure that I do more than things right, but the right things!
  • to REVIEW: I can check the progress on what I have done weekly “You can only manage, what you can measure”

Tools you need are:

  • asana

The todo workflow:

[ordered_list style=”decimal”]

At the project beginning I start with the planning game

  1. The “customer” is asked for the desired features. This features are the goals/use stories/hypothesis. The customer can be an external person or myself. Important is the interview technique for this. This is done by brainstorming  and writing the general hypothesis for the process steps down in asana.
    1. New Tasks are added with Tab-Q: I select an action title, a description like an web url, assign it to the person and select a project Title: Write down the result, with specific words and details … so that a assistant could do it.
    2. Go to my Inbox (Task assigned for me within 1 day) and priorize the tasks according to the eisenhower matrix
      1. Important: What happens if I don’t do it? Does it damage my career (3), damage my personal relationship(2), damage my health/self(1).  (Tab-H) Write down the goals for the next 1-2 years and what has to happen (persons liking you, …). If a task contributes to goal then it is important.
      2. Select all and send to upcoming (Tab-L)
      3. Urgent: When is it due? Give a date otherwise check in a month! (Tab-D) Date: Have always 3 days puffer!
  2. The “engineer” estimates the difficulty of the task.
    1. By creating dummy subtask for every (25 min pomodoro).
  3. Decide on the goals/hypothesis for the “2 week sprint”.
    1. identify the right question to prove the hypothesis and the test assessing that the goal has been done.
    2. Break the selected big goal down into small 25 minute tasks. This is important so I am not overwhelmed and also that I can do work in small breaks. 

Start working from Category 1 to 4.

  1. Short term todos that impact my long term goals. Do them now and with high accuracy. Try to prevent this the next time by planning better or saying no / telling somebody that I don’t appreciate such short notice work.
  2. Not urgents things that impact my long term goals. I plan specific times to do this todos with high accuracy.
  3. Not important to long term goals but urgent. I delegate them or do them quick by the 80/20 rule.
  4. Not important and not urgent: Do I really have to do them?

Do a Daily Scrum everyday after waking up 3 minutes:

  1. What did you do yesterday?
  2. What will you duo today?
  3. Are there any impediments in your way?

[/ordered_list] 

[hr]

agile principles: 
  • Collective Code Ownership:
    • find feedback groups for everyproject and demand active feedback.
    • as well as put my “code” online so everyone in the group can track and improve it.
  • Small Releases
    • Integrate so you have always  a complete version at the end of the day.
  • Simple Design
    • Just a short structure how to reach the goal. Work with hypothesis and try to prove them. Use this to break down big goals into small tasks.
  • Customer on site: 
    • Always be in close contact with the customer.Check at least once per week (either with a significant improved version or a question catalogue that is need to overcome the challenges that prevented the significant improved version last week).
  • Refactoring:
    • Don’t plan extensively for every eventuality. Focus on the next sprint. If something is wrong, change it.
  • “Coding” standards:
    • Define standards and make them available to everyone that works on the project and inform yourself on existing standards in the project. Publish your standards on your blog in the category workflows.
  • Test driven development:
    • Before you start “implementing” / prove the Hypothesis define the test when the hypothesis is proven or the goal is reached. E.g. What questions does a reader have to answer after a chapter? Check this by letting somebody read the chapter and ask the question).
  • 40h week:
    • work a maximum of 40 hours per week. Track this.
  • prototyping:
    • If you are not sure if this is the right way. Start with a prototype and experiment and learn by “try and error”. Like instead of writing a complete chapter make a fast research round and then write a short agenda/draft for a chapter.

10 most important skills in business

There are 10 skills that are highly valued by the market.

Business and Students often complain that university and school does not prepare them for the future. The results of a survey from the National Association of Colleges and Employers shows what are the critical skills needed in the market:

  1. Communication
  2. Teamwork
  3. Decision making & Problem solving
  4. Ability to plan, organize, and prioritize work (Planning)
  5. Ability to obtain and process information (Information Literacy)
  6. Ability to analyze quantitative data
  7. Technical knowledge related to the job
  8. Computer software programs
  9. Create and edit written reports
  10. Ability to sell or influence others

In this series I will “MOOC based self-education degree” in “Essential Business Skills”. The goal is to brush my own skills up and create a comprehensive program available to everyone. In the next week I will start with communication.

The idea is inspired by http://dailyplanit.com 

Storytelling

Storytelling is one of the oldest and most powerful forms of communication. A good story well told not only increases audience attention, but is also better remembered than a list of items or facts.

Best Practices

The essential parts to a story — Every story consists of a few essential elements: an initiating incident, a protagonist, action, and an outcome. Unless your material comprises these elements, it won’t be perceived as a story.

[toggle title_open=”Close Me” title_closed=”Open Me” hide=”yes” border=”yes” style=”default” excerpt_length=”0″ read_more_text=”Read More” read_less_text=”Read Less” include_excerpt_html=”no”]

Just telling about an event is not always a story. Not all narratives are stories. A story contains four essential components:

1. Initiating incident. A story must have an impetus, a cause that drives someone to take action. In most stories, this is a problem — or an opportunity. Whether it’s negative (a problem) or positive (an opportunity), the more extreme this incident, the more compelling the story will be.

2. Protagonist. A story has one or more individuals (a team, organization, etc.) trying to achieve a goal caused by the initiating incident.

3. Action. The protagonist takes action to address the problem or opportunity. The story becomes more engaging if obstacles stand in the way of achieving the goal, and make it harder to obtain. The protagonist’s actions to overcome the obstacles can be the most instructive elements in stories.

4. Outcome. Once the problem or opportunity has been revealed and action taken by the protagonist, the audience will want to know what happened. Did the protagonist achieve the goal? Whether your story has a happy ending or not, the outcome must be clear.

Of course, simply having these four elements does not guarantee that a story will be memorable, instructive, or even interesting. It just means you have a genuine story. A story needs something more if it’s to stick.

[/toggle]

Examples of effective storytelling — Exemplar video stories illustrating IBM’s core values.

[toggle title_open=”Close Me” title_closed=”Open Me” hide=”yes” border=”yes” style=”default” excerpt_length=”0″ read_more_text=”Read More” read_less_text=”Read Less” include_excerpt_html=”no”]

  1. Innovation that matters — for our company and the world
  2. Dedication — to every client’s success
  3. Trust and personal responsibility — in all relationships

[/toggle]

Giving your story impact — But compelling stories need more than just the basic elements. Here you’ll learn storyteller “secrets” on how to make a story more powerful.

[toggle title_open=”Close Me” title_closed=”Open Me” hide=”yes” border=”yes” style=”default” excerpt_length=”0″ read_more_text=”Read More” read_less_text=”Read Less” include_excerpt_html=”no”]

Making your story memorable

We suggest you watch each of the video examples in the previous section (Examples of Effective Storytelling) before your review this section.

Each of the video examples had the four basic elements we identified earlier: initiating incident, a protagonist, action, and an outcome.

But these stories go beyond those basic requirement.
Below are story-strengthening elements that can raise a story’s impact. Incorporating any one of these elements can help — adding several can help even more. But whatever element you add, be sure it is genuine and appropriate, not artificially invented to try to increase your story’s power.

1. Something important at stake. A major risk will ratchet up audience interest in a story. In Dick Richardson’s “Mazel Tov” story, IBM attorneys discovered Dick’s omission of a required Sexual Harassment component in the manager program — his own career was in jeopardy because of his mistake. We want to learn what happened!

2Time lock. When a problem or opportunity has a definite deadline, it creates an urgency in the story, raises the tension and peaks audience interest.
3. Expectation violation. When audience expectations are dashed — for a good reason — the story soars.

4. Parsimony. Clutter is the downfall of an otherwise excellent story. A good story has just enough details to establish the situation and characters and move the story events forward. “Parsimony” is the absence of clutter. Aim for it.

5. Reveal information only when needed. One good way to ruin a story is to provide too much needed information all at once. Good storytellers “dribble out” the necessary background as the story is being told, usually just before that information is needed.

6. Obstacles. The initiating event causes the protagonist to take action. But if the goal is easily attained, the story won’t generate much interest. The story really crackles when a protagonist has to be clever or courageous or fortunate to overcome obstacles.

7. Abnormality. Stories stand out and are better remembered if there’s something unusual in them. In Todd Belt’s Katrina story the IBM technicians load their motor home with diapers and other items and head out on their mission. Afterwards they help dig out a homeowner’s possessions from four feet of flood sewage. These memorable descriptions send a striking and important message about this unusual endeavor for IBM techies.

8. Visual salience. A memorable story paints pictures in people’s heads by using visually descriptive phrases that connect with the audience. Dick Richardson begins by saying, “It was a pizza-box-in-the-hallway kind of project,” implying that it took the team an all-hours effort. In her Mentoring story Anne McNeill says the rural school teacher “literally had tears in her eyes” when expressing appreciation to IBM. Using visual description is a solid storytelling technique.

9. Formidable antagonist. In some stories the protagonist must face and overcome an adversary or “antagonist.” It could be a corporate competitor, an uncooperative colleague, or a force of nature. A formidable antagonist makes the story that much more compelling.

10. Underlying meaning. A story worthy of telling carries meaning. The more important the meaning, the more important the story. Sometimes that meaning is explicit and stated, sometimes not. But to lead and instruct, a story must have meaning, or else it simply entertains.

You’ve probably noticed that many of the requirements for good storytelling are the same as any good communications technique employed in a business setting. It must be concise, accurate, clear, impactful, and readable. In today’s world with remote management, virtual teams, and cross-border projects, communications is more important than ever.

[/toggle]

Tools / Job aids

Story capture rubric (18KB PDF) A simple tool that will help you: establish the strength of a possible story, begin to outline the essential elements, and confirm what might be missing to build an effective story.

Storyboard template (111KB PDF) Storyboarding is a series of illustrations or images displayed in an order that shows the progression of a completed motion graphic or interactive sequence. The illustrations may be photos, film clips or rough sketches. Each illustration often has notes describing any dialogue, action and/or special effects (FX) that accompany the scene.

Video production outline.pdf (24KB PDF) Bare-bones list of steps to follow for producing video for learning

[Video Captioning Tutorial] Learn how to create a well structured, designed and impactful videocasts.

FAQ

I don’t think I have any particular talent for writing or telling stories, but I can see situations where they could be effective. Are there ways to develop this skill?] Yes. Classes in creative writing are widely available, as are storytelling workshops. Toastmasters International offers an enjoyable and supportive atmosphere for improving your public speaking talents — crucial to effective storytelling. We all know people who seem to be “natural-born” storytellers. You are correct though in recognizing storytelling as a skill, and like most other skills, storytelling can be improved with knowledge and practice.

Presentation Workflow

To cut down the time I need to create presentations with others I define the presentation creation process:

[ordered_list style=”decimal”]

  1. First open the

    This slideshow could not be started. Try refreshing the page or viewing it in another browser.

    in the office skydrive and create a copy of the template with the following name: yyyymmdd-topicdescription.pptx
  2. Get an overview of all available template with STRG-2.
  3. Then scroll down to the end of the template after the black slide and fill in the presentation topic.
  4. Then define the agenda on the next slide (breaking the presentation task down to smaller more workable junks).
  5. Create a storyline for every chapter. Creating action titles for the slides.
  6. Add notes for the content to the slide.
  7. Research the information for the slides.
  8. Then select the optimal slide template for your information.
  9. DON’T FORGET TO SYNC THE PRESENTATION TO THE SKY DRIVE SO EVERYONE CAN WORK ON THE PRESENTATION.
  10. Don’t forget to spell check!

[/ordered_list]

For a quick overview presentation or a informal occasions use your Pecha Kucha slide. For a short overview wach the following video:

 Presentation Tips:

  • Spann einen roten Faden!
  • Erzähl Geschichten und untermauere Deine Erläuterungen mit Beispielen
  • Beweg dich und klebe nicht am Rednerpult fest!
  • Verschwende keine Zeit mit deinem Ego und überzogener Selbstdarstellung!
  • Stell Fragen, egal wie groß Dein Publikum ist!
  • Lass Bilder sprechen!
  • Mach es (an)greifbar!
  • Schau über den Tellerrand und präsentiere Ideen out of the box!
  • Baue Spannung auf!
  • Bring Dein Publikum zum Lachen!
  • Leidenschaft zählt!
  • Lass Dich von anderen Referenten inspirieren (achte auf die Dosis), ohne sie zu kopieren!
  • Hole Dir immer ehrliches Feedback ein (Fragebögen sind diesbezüglich nicht geeignet)!
  • Gebe den Menschen zum Schluss immer etwas mit, egal ob Hausaufgaben, Deine Kontaktdaten, ein GiveAway bzw. Handout oder eine Handlungsaufforderung!
  • Bleibe nicht an Deinen Folien “kleben”, sondern sprich frei, ohne den roten Faden zu verlieren!
  • Nicht die Technik oder Gimmicks, sondern Deine Botschaft sollte im Vordergrund stehen und unvergesslich sein!
  • Wiederhole Deine Kernbotschaft(en), gerne auch in unterschiedlichen Worten!