This is an awesome rule to follow if you want to get things done (GTD).The 70-20-10 model suggests that lessons learned effectively are roughly 70% from tough jobs, 20% from people (mostly the boss), and 10% from courses and reading. It applies to learning, innovation , savings and marketing, conducting organizational change, content management many other fields. Just follow 70-20-10 model.
Showing posts with label GTD. Show all posts
Showing posts with label GTD. Show all posts
August 29, 2013
The Rule of Getting Things Done - 70-20-10 - Studying Versus Learning
August 18, 2012
PDCA psychology – Continues improvement (and kids video games)
True PDCA (Plan, Do, Check, Act.) is all about
the ability to respond to change, constantly improve, gain sense of ability, change and grow while
making forward progress. How can we use it to the benefits of the
family?
My kids are now old enough to play video games. This has, of course, got
me wondering about the benefits of playing those games, if there are even any
benefits. Well, they have SOME
benefit. When you fail, or experience success, or need to get things done to
win the game (remember this post?). It’s an excellent example, of what a PDCA (Plan, Do, Check, Act.) is all about.
“ There is another aspect of failing in video games that I think we need to pay attention to, and that is the role of autonomy. ….The reality is that mastering challenges and
fun failure creates a feeling of optimism, which neurologically and emotionally
improves our ability to learn in the future. If we think we are capable of
solving a problem, we will keep at it. Therefore, we need to foster a sense of
autonomy in learning. The minute we start talking about “my special needs
child,” we are taking away their autonomy…The less we stigmatize failure, the
more we encourage autonomy and optimism. Autonomy and optimism make you a
better learner, a better collaborator, and a better worker. Personally I think
the world could use a lot more of that.” Mike Langlois
And I will argue the additional point, that those video games allow the
kids to fail over and over again, forcing them to re-plan their steps and try
again. Gain more experience and try yet again. Failing again and again just
means that you learn how to do it better next time. And each time you re-start
the level, you gain in abilities, or power, or wealth. You start from a
relatively easy stage and advance to harder and harder stages, journeying
through a series of failures, successes and learning.
And so, thinking of the video gaming experience, I think it’s an
excellent example, of what a PDCA (Plan, Do, Check, Act.) is all about.
The ability to constantly improve, gain sense of ability, change and grow while
making forward progress.
Lets leave the kids playing their video games, and learn a bit about
PDCA, and how we can use it in the family.
According to Wikipedia, “PDCA (plan–do–check–act or plan–do–check–adjust)
is an iterative four-step management method used in business for the control
and continuous improvement of processes and products. ”
When do we use it?
● As a model for continuous improvement.
● When we wish to implement any change
● When we wish to improve
● ….
Plan to do something → Do it →Check and see how it went , Change
whatever you think is needed to change →And Act accordingly to the changes.
Then do it again.
Take a task (a small one) and place it on the board:
(I will add the F - for Fun)
When we start using PDCA more and more, it becomes second nature
to us. Just like a child playing a video game, failing and checking our steps
is something that comes without thinking.
It’s a continues improvement mindset approach.
When done right, I believe that PDCA keeps us in a “capable “mode. It
challenges us to solve problems in relatively small portions, allowing us to
experience small failures and experience a change to success.
By the way, ‘Failure’ isn’t a bad word; it’s something that when
experienced in small doses can be manageable and helps us progress and achieve.
‘Success’, of course, is a great feeling - and we can use this feeling when we
make small changes. We don’t need to wait for the big bang process to be
completed.
PDCA, when done right, helps us experience controlled success and
failures, and most important, helps us feel capable, driven from our experience
and the effort we put into ‘doing’. This fuels us to continue, to try solve and
change and grow.
Of course, just as anything else unfamiliar, the theory looks very
strict. We just need to experience it, adapt it to fit our needs and improve on
it.
So , what is the best way to get into a continues improvement using
PDCA?
1. Don’t forget to have fun while changing .
‘Fun’ usually comes last in my checklists. Not this time. Having fun helps fail better and increase the ability to solve problems now and in the future.
‘Fun’ usually comes last in my checklists. Not this time. Having fun helps fail better and increase the ability to solve problems now and in the future.
2. When something is interesting it’s also easier to solve.
PDCA is like a puzzle, so treat it as such. It should be interesting and related to what we want to do. Like in puzzle, we need to try sometimes few times before we figure it out.
PDCA is like a puzzle, so treat it as such. It should be interesting and related to what we want to do. Like in puzzle, we need to try sometimes few times before we figure it out.
3. Encouraged Autonomy.
In a video/PC game, you start from the easy stuff. You gain experience by failing and retrying (do-check), you learn from your mistakes and try again. Sometimes (most of the times!!!) you become better… even awesome in what you do. But the player manages to do it since he can use the autonomy of the game. This is a very important step in PDCA. Have the autonomy to change, learn and adapt. No change will happen if you aren’t allowed to think by yourself, fail, make mistakes and try again.
In a video/PC game, you start from the easy stuff. You gain experience by failing and retrying (do-check), you learn from your mistakes and try again. Sometimes (most of the times!!!) you become better… even awesome in what you do. But the player manages to do it since he can use the autonomy of the game. This is a very important step in PDCA. Have the autonomy to change, learn and adapt. No change will happen if you aren’t allowed to think by yourself, fail, make mistakes and try again.
4. Welcome failure as a step toward success.
Don’t expect to succeed from step one. Encourage your family to check things out and try again and again.
Don’t expect to succeed from step one. Encourage your family to check things out and try again and again.
5. Deal with small steps, one thing at a time.
There’s no need to plan, do check and act over massive projects. It doesn’t need to be a long cycle. It can be a daily process of planning, doing, checking and acting. Divide big changes into smaller practical tasks. Pick up one at a time and go with it.
There’s no need to plan, do check and act over massive projects. It doesn’t need to be a long cycle. It can be a daily process of planning, doing, checking and acting. Divide big changes into smaller practical tasks. Pick up one at a time and go with it.
6. Check – means communicate, talk it over, discuss.
Ask what went well and what can we do differently. You can use the daily gathering for that.
Ask what went well and what can we do differently. You can use the daily gathering for that.
7. Ease yourself out of your comfort zone.
Do one small thing each day to challenge yourself. Feel uncomfortable once a day, check it out, learn and adapt the next day.
Do one small thing each day to challenge yourself. Feel uncomfortable once a day, check it out, learn and adapt the next day.
8. Learning is a curve.
We learn better from experience.
We learn better from experience.
9. Appreciate the effort of doing.
It is highly important especially when you don’t succeed.
It is highly important especially when you don’t succeed.
10. Visualize.
As always, when you can see the change, it increases the probability of changing and doing.
As always, when you can see the change, it increases the probability of changing and doing.
By the way, to visualize, I take a small enough
task , using sticky notes, place them on
the board, run them visually into the PDCA process, and until people don’t even see the process
anymore it’s so innate, I mark the change visually on the board.
Well, I’m off to play some video games. Can’t let my boys grow TOO
complacent :)
To read more:
תוויות:
agile family,
children education ; agile at home ; agile kids,
focus,
fun game,
Goals,
GTD,
PDCA
August 15, 2012
Going back to school schedule
Remember when your
kids spent the last month following a daily schedule, going to bed early,
getting up early, and setting aside time for their homework?
You don’t?
The holidays might
have had something to do with that :) Kids tend to sleep late, lose track of
time, have no schedule whatsoever - but they’re kids. They are allowed to.
But school is just
around the corner, and you need to start getting back on track.Going to bed at
normal hours, setting a daily schedule, and so on.
How do we do that?
1.
First,
we’ll refresh the basic rules.
a.
Bed time.
b.
TV
schedule.
c.
Homework
place and schedule.
d.
And
of course, any other rules that matter.
2.
Gradually
get back to track :
a.
Pick
a few issues to start changing, and practice them.
b.
Retrospect
each day over the results and select the next issues.
c.
Insist
on getting tasks done.
I’ll finish this
post with some practical tips of getting kids ready to go back to school - Enjoy!
July 14, 2012
Brainstorming your initial to-do list
You’ve just started out with your
first to-do list, looking at an empty whiteboard, and all of a sudden you have
no idea what to do first, or even what to do.
You need ideas.
Brainstorming is an AWESOME
tool for generating ideas.
In this case the way I see it,
generating ideas is the first step towards starting and managing our backlog. Luckily,
we can use the brainstorming technique at any point of the backlog elaboration.
Ideas that come from these brainstorming sessions can be turned into ‘user
stories’ or goals for our backlog.
Now, I’ve gone with the simplest
possible way to brainstorm, just to show you what I mean. If you want to do
some more research (always a good thing!), I’ve put some recommended links at
the end of this post.
So why would we use
brainstorming to start a backlog?
●
When we have so many ideas, we
can’t pick the ‘really important one’.
●
When we want to refine and
redefine our backlog with ideas that are really worth working on.
●
When we run out of ideas.
●
When we want to get others
involved with creating our backlog.
●
When we introduce the backlog and
to-do list for the first time, and we want to break the ice.
An example of using a
brainstorming session to improve parent participation
A group of teachers I know was
trying to find creative ways to get parents to be active participants in their
next Parent-Teacher day. They were going with a central theme of ‘Creativity
with Children’, and they wanted to follow through from theory to practice.
Now, there are a lot of ways to
tackle this subject and get things done, but of course the teachers needed to
select the right ideas, so that other teachers would follow through as well.
The last thing they wanted to do was dictate ideas to the other members of the
faculty. Not only will this immediately create antagonism, but teachers that
worked with the children daily would have a much better idea of what would work
and what wouldn’t.
So they went with a short
brainstorming session. This enables each participant to toss out ideas for all
to hear, seeing the ideas on the board during the session can create new ones
that weren’t thought of before, and of course, deciding on the ideas together
raises the level of commitment to the meeting’s decisions.
Among the many good ideas, there
were “baking a cake together”, “football session with kids”, and even “building
a city model“.
After shifting through the ideas
and discussing them, the teachers picked out four ideas. Each one became a
backlog item, which they then divided into tasks, which of course made it
easier to follow through the idea all the way to the end.
So how do we brainstorm our backlog?
(One suggestion out of many)
The brainstorming session
outline:
First, the basics:
1.
The facilitator should make sure
the rules are kept and run the session openly and smoothly.
2.
Group members can vary between 4
to 30. Smaller groups are easier to control but there will be fewer ideas to
present.
Second, the presentation:
Gathering the group, the
facilitator must:
1.
Present a short description
of the brainstorm session and the expectation of creativity.
2.
Present the rule that the
brainstorming session allows everyone to participants and remind the
participants of the fact that all ideas must be heard.
3.
Present the main
problem/need/ example and the desired outcome.
4.
Set a time limit.
5.
Announce the “go” to start
the session.
6.
Make sure the session
outcome is recorded to a place we can later visualize, comment and rethink. I, of course, prefer a wall with sticky notes.
The brainstorm session:
1.
Each group member writes down
their ideas or solutions.
OR
OR
There’s an open discussion, with ideas being tossed around and written down on
the board.
2.
Encourage discussion
a.
Open with asking for
“ideas” that springs in mind ; continue
by asking people to use each other’s ideas to think of new ones; ask them to
ignore the execution phase for now; ask them to
suggest all ideas not only the interesting ones; and then continue with
asking for “radical ideas”.
b.
Give positive feedback and
encourage the group to continue – don’t judge the ideas or the people!
4.
Now you should have a lot
of ideas on the wall.
Analyzing the ideas:
1.
Once all the ideas are on
the board, group them into five to eight groups of identical area.
2.
Ask the team to vote for
the ideas. Each member has a number of points equals to the number of ideas,
minus two. He need to give points to the ideas that he thinks are the best
answer to the question first put to them by the facilitator.
3.
Pick the ideas with the
most points, and ask the team: who, where, why, how, when, to get them to
elaborate a bit over the ideas selected
(At this stage, we can use
working groups, dividing the group into smaller working groups. Each group
takes one idea, and brainstorms it further, before presenting it again to the
main group)
Remember, this session alone, may
completely change the initial ideas and bring few more.
4.
At the end of the
brainstorm session, we should have few ideas/goals as our main backlog items.
Those ideas can later on be assigned to working groups and divided into smaller
tasks processed into the flow of work till achieved.
Take a look at this flow of
brainstorming; it can also be done with two people, or a personal
brainstorming. And now that you have some tasks and a backlog, use Scrum and
Kanban to start getting them done.
Want to read more about brainstorming?
● Osborn, A.F. (1963) Applied imagination: Principles and
procedures of creative problem solving (Third Revised Edition). New York,
NY: Charles Scribner’s Sons.
● "Productivity Loss in Brainstorming Groups: Toward the
Solution of a Riddle". Journal of Personality and Social
Psychology 53: 497–509. 1987.
● Stroebe, W.; Diehl, M. & Abakoumkin, G. (1992). "The
illusion of group effectivity". Personality and Social Psychology
Bulletin 18 (5): 643–650.
תוויות:
Agileathome,
Brainstorming,
GTD,
kanban,
kids scrum
July 07, 2012
Be like God - Kanban your way into the world
Whether you believe in God or not, the story of Genesis
is an excellent example of doing one thing at a time.
As you probably know, God created our world in just
seven days (vacation included)- by completing one major deliverable every day,
which was made up of smaller, manageable tasks.
Of course, things are never that simple. On the third
day, God completed not one, but TWO tasks. Why? Wait for the end of the post to
find out :)
So what do I mean by saying that God does Kanban
and God has a limited WIP? I actually mean, that God avoids multi
tasking and getting things done by controlling the load of its tasks.
Well, WIP, as you know, is Work In
Progress. In Agile, it refers to all materials and partly finished products that are at various stages of the
production process.
Comparing it to an industry production line: In Genesis,
God put his materials in one end, ran it through the production line, and got
the magnificent outcome on the other end - Our world.
Don’t take me literally,obviously, but just look at the
pattern here. Each day, God selected one deliverable with a related value,
and each deliverable was composed of few small tasks, each done one at a time.
At the end of each day (deliverable) God took one step back, looked at the
creation (demo), and took up where he left off the next day.
This is an excellent example that shows you about WIP
limitations. Doing one thing at a time, and challenging yourself to achieve
more according to your limits. Obviously, God doesn’t have a limit. But perhaps
he was trying to teach us to do one thing at a time, by example.
Control your WIP (work in progress): It’s simple. When we do more than we can
handle, we probably won’t complete anything. Starting a lot of tasks at
once, doing a little bit of everything, means that you finish late, or not at
all. This also means that we have to understand what we are capable of, the
size and issues we can grasp in one time.
Start finishing and finish starting.
Doing just a little bit from everything means you
don’t do anything.
An easy example of limiting your WIP is having to
attend two meetings at the same time. That’s easy. You pick one - and go to it.
But what about preparing a presentation, writing a blog post, checking your
email, preparing for a meeting with your team, and researching stuff for your
manager. If you start all that at the same time, you won’t get any of it done,
and you’ll end up missing your presentation, not answering all your emails, and
meeting your team unprepared.
Now think about your kid. You’re telling him to clean
his room, do his homework, feed the dog, clear the table, brush his teeth, take
out the trash.... that could confuse even God :)
So how do we handle it then? How can we create our own
small world, in such we can do valuable things and deliver the outcome?
Start off by making it clear (to yourself as well) that
you are expected to do ‘one thing at a time’.
Then, order your tasks by schedule, priority or
importance.
Make sure to start doing things with value first.
So lets take the previous example. You need to prepare
a presentation next week? Start today by creating the presentation outline
(‘Small task’) and send it along to get early feedback. Treating the ‘prepare
presentation’ task as one big one means that your definition
of
done
means that you have to finish the presentation today. This will affect your
ability to complete your other tasks, so make sure you start and finish the
scope of work as you defined it. Don’t leave unfinished tasks around.
Pick one task, complete it , and then take the next
task in line. In time, you’ll see how many tasks you can perform at
the same time, but to start off with, it’s better to complete one task at a
time, than start five, and not complete any of them.
In industrial factories, an incomplete cycle of work is
called inventory. Factories can’t sell inventory. Inventory takes up space,
which you pay for. Inventory needs to be maintained, which you pay for.
Inventory is waste.
In our personal life, we pay for that wasted inventory
with delays, stress and overtime, just because we try to keep up with too many
tasks.
Context switching (jumping from one task to another
without completing either) is another way to get little or no value from our
tasks.
A nice story a friend just told me the other day about
a typical Kanban situation at home illustrates another example of the same
problem:
“It was Friday noon, and we were preparing for our
daughter birthday party. I was with my hands in the pizza dough, and my wife
said: I can’t really help you, so I’ll bake a cake for us to eat during the
week. In theory, there’s no problem. But when I needed the blender, it was
dirty with chocolate and I had to wash it. When I wanted to use the oven, I had
to wait 40 minutes for the cake to be done.
I should have told her to just relax and drink some
coffee, or put some music and chat with me, instead!”
The value = daughter birthday party ➔ pizza : was not achieved
The resources= help from others with the blender, oven.
: was not available
Over doing =using the oven as a resource to bake a cake
while at the same time the pizza (which holds more value) needs the same
resource.
Following the concept of ‘doing one thing at a time ‘
will be made easier when you visualize your tasks on a task board. The
task board will help you see your tasks, prioritize them, understand your
limits and challenge yourself toward improvement.
So… doing one thing time, it’s easier
when , We understands
that :
- When we do more than we can handle, we probably won’t complete anything.
- Context switching (jumping from one task to another without completing either) is another way to get little or no value from our tasks.
- Doing just a little bit from everything means you don’t do anything.
- Start finishing and finish starting.
So the actions applies will be:
1.
Visualize your tasks. Use a
task board.
2.
Set priority to the things
you need to do (see important vs urgent)
3.
Pull one task, complete it ,
and then pull the next task in line. make sure you start and finish the
scope of work as you defined it. Don’t leave unfinished tasks around.
4.
Divide big assignments into
smaller ones that have value (see how God took two small tasks on Tuesday?)
5.
Understand your resources and
limits demanding to perform the tasks.
6.
Stick to doing what has the
most value – even if it means not doing something else.
7.
Look back at your results.
Retrospect and change if necessary
8.
Learn and adapt to your abilities.
Once in a while, challenge yourself to take more tasks (although not in
parallel!), just as God did on Tuesday.
Enjoy ☺
Read more in this blog:
Subscribe to:
Posts (Atom)