It all started when I came across an ongoing Gizra calendar event with the title ‘Scrum’. I didn’t know the word and I wasn’t invited to these meetings. But it was something unfamiliar, and my curiosity piqued. So I used Google Translate, but the result I got did not make any sense:

Google Translate, as any native non-English speaker knows, is not precise and sometimes translates words in funny ways, but this was too much. What was going on in the meeting room?!

Well, because I didn’t hear strange noises from the room, and didn’t see anybody walking around dressed like rugby players, I realized that I was probably missing something.
So I asked the father of Google Translate - Google itself. Things were starting to make sense and I was fascinated.
I found myself rolling from one article to another, reading about the Scrum method with enthusiasm.

When I started to work at Gizra three months ago, I received the title ‘Employee Training & Development’. Even though this was exciting to me - I get excited with anything that has the word ‘training’ in it - I was not really sure what I should do with it. The exposure to the Scrum method helped me think about my role in Gizra.

As Scrum is based on the Agile methodology - an iterative light-weight approach to software development - and unlike traditional methods, it is built on the premise that it is impossible to think in advance about all the possible scenarios. In a dynamic world, especially when it comes to software development, changes occur all the time: new demands by clients, market changes, new technologies, and so forth.
So the more I read about Scrum, the more I realized that Gizra’s training process needs to also be agile. What we teach today will not necessarily be useful to employees tomorrow, so the training program should be built in a way that is flexible to changes and new requirements.

I don’t know of many 20+ employee companies that make the decision to invest a full-time role to employee training. Frankly, I don’t know of any.
For me, it says something very important - Gizra wants to invest in their already great employees to make them even better.
But how do we get there? This is a question that I still don’t have a full answer for.
So in the meantime, I will just share my thoughts.

Teach them to swim or throw them in the deep end?

Do employees require organized training or should we just show them the pool and let them reveal things for themselves? In other words, who is responsible for learning, the employee or the trainer?

When I came to Gizra, they threw me into the deep end. The water in Gizra is very deep!
It was a frustrating experience. I know how to swim and I did all the moves, and yet I felt a lot of times that I was drowning. It was a new pool, a different water temperature, and it took time before I learned to take a rest in the shallow water, and where the ladder was located so I could get out.
To tell you the truth, I’m still learning.
For a new employee, it is a very inconvenient experience, even stressful, and I admit that sometimes I flirted with the thought of going back to my previous job, familiar and cozy, where I knew how to swim well.

What kept me going is the very early understanding of “The Gizra Way” that allows you to make mistakes. The message is clear: the important thing is to keep doing, make mistakes and do better next time. I realized that nobody would fire me because I was wrong, as long as I took note of my mistakes, learned from them, and made all the efforts not to do them again.

An organized training plan’s main advantage is that it facilitates the entry process, which is already difficult. It prevents added frustrations and allows for more rapid learning. From the first moment an employee understands what is expected from her, the knowledge is gradually built, and she makes less mistakes. I believe that this significantly shortens the “newbie” time.

On the other hand this process can create passive workers - they just need to come to class and they will get all the answers.
When someone is thrown into the deep end, they must be active. Learn the movements on their own. The message is that you have responsibility for your learning. There is value in questioning and self-discovery, and it encourages initiative.
I think when a person finally figure out something on their own, they get much greater satisfaction.

In the web development world, where things are quickly and constantly changing, this is a very important skill to learn alone. All of this should take place in an environment that demands excellence, but still lets you get it wrong and learn from mistakes.
I found this environment at Gizra and we need to preserve it.

However, I am still trying to find the right formula that would combine structured learning and independent study.
What topics are important to teach in class and what should be left for independent study?
How to encourage curiosity?
How to create a safe and comfortable atmosphere for self-study?
How to make frustration a motivator instead of a source of despair?

And what about the good of the company? What is the fastest way to train an employee? How much breathing room does Gizra have to absorb mistakes?

Google is our best friend

Throughout the learning process, it is very important to convey that we should not be afraid to say ‘I don’t know.’ No one expects you to know everything, especially when you are a newbie.
To be honest, at this point, I am still a newbie myself at Gizra. I feel that there are more things I don’t know than things I do.
On the other hand, don’t give up on yourself. Not knowing should motivate you to act! Have you heard any concept that you don’t understand? Have you come across a tool that you don’t know what it does? Google it! Keep asking, and don’t stop, until you know.
Good employees are employees who know their job.
Excellent employees are employees who know what they don’t know, and continue learning.

Who knows better, the teacher or the student?

The basic premise we have become accustomed to is that the specialists should teach. Big companies that have organized training department, let experts (external or internal) provide training on topics in which they specialize.
But what about small companies that have a smaller number of employees and limited resources?

Gizra is technology intensive and is constantly searching and adding new and better tools to its stack. People come from all kinds of backgrounds and with different levels of knowledge on various technologies. Therefore, it is clear that there are more than a few topics that employees know better than me, the trainer.
This point bothered me greatly. At first I thought I should take all the responsibility on the knowledge - the trainer has to know everything about what she has to teach. I quickly realized that even though I really wanted to, I can not know everything. However, whatever I do teach, I teach really well.
So, I understood that it is important that I have excellent training skills, but still, how do I bridge the knowledge gaps?

In my far past when I worked in the Education field, before I entered the web development world, I worked in a wonderful place called The Secular Yeshiva. This is a place where secular people learn and take responsibility for setting their Jewish identity.
One method, that is still with me today, was the ancient Jewish method - Hevruta (learning with partners).
Hevruta is about learning in small groups (3-5 people), and the idea is that the group is a space where no one has authority over knowledge. Learning occurs during the exchange of ideas and knowledge-sharing among participants.

Well, if knowledge is also in the workers heads, let’s get it out there and share it with everybody.
In the pedagogical world, it’s called Peer Learning. In other words, students teaching each other. In this way people are given the opportunity to demonstrate their knowledge, the message is that everyone has a responsibility for learning, and to teach. It’s a start of creating a culture of contribution and sharing of knowledge.
How to implement this? Well, I am still thinking about it, promising to update in the next post.

What to teach?

Should we be training on technology, or skills and practices?
Where to start? There is so much to learn and who should know what?
One of the principles of Scrum is that everyone needs to know everything! This way, everyone can perform any task (characterizing the structure, testing, Front end, Back end, etc.), so if there was a strain on one team, another team can help out.
In addition, project managers, marketers and even customers need to understand the basics of development work, to create a common language for more effective and clear communication.

Therefore, we need to find a way to create a learning program that works for everyone. We should take into consideration that developers come with a different set of concepts than project managers, and therefore the training should be able to be adjusted.
For example, when talking about How to approach a new task, developers will be very clear with terms such as query and relationship, but they may have difficulty explaining it in literal terms and go straight to talking in programming language.
Marketing and project managers would rather easily understand the story, since most of their work is to understand the customer’s needs, but may find it difficult to break it down to entities and identify the relationships between them.
If we want to create a common language for everyone, we need to understand these differences and consider them during training.

What about a Training Plan?

I am, by nature, a very planned person. I am used to working with well defined goals and to release a product only when it is complete. Therefore, my natural tendency was to start work on a training program, and only then begin with training sessions to the employees.

Well, that didn’t happen. On the second week on the job, I found myself teaching a subject that I just learned a few days earlier. It felt like they threw me into the deep end from a height of an Olympic springboard - it was so high I could hear myself screaming before I hit the water.
I’m not used to being anything less than an expert on a subject that I teach. I did it but I was not at all convinced that this was the right way.

But then I came across Scrum and the more I read, the more things fell into place.
Unlike traditional methods which have detailed documents defining goals and objectives, Scrum has concise lists (backlog) and a lot of face to face interaction with all the people involved. In addition, there is an emphasis on achieving efficacy - how many useful things were created in a given period.

If I stayed with my familiar method, it is likely that for the first two months I would have spent on builds a training program, learning content, preparing lessons, and only then started teaching.
In practice, today, only three months into my new job, I have taught 15 classes on 5 different topics. At this rate, I am excited to see where we will be in a year from now.

Was my first training session any good? No, and of course it could have been much better if I had more time to study the subject and prepare. But going back to the Scrum model, it was the best training version I could release at that time. I knew I had enough training sessions along the way, so I could improve while doing.
If I did not jump into the deep end so early, I would probably, only now, be giving the first training session. I may have been more confident standing in front of the class, but moving forward at a much slower pace. Even this post couldn’t be written because I wouldn’t have understood a lot of things I understand now.

It is still hard to shake off old habits and even when I am writing these sentences I find it difficult to release and say, this is a good enough version of the post. There are a lot of open questions, and I still can not fully answer the question: how to set up a training program in a small company.
But I remind myself to think “scrum” and say: “Let Go! Even in Rugby they don’t stay with their arms interlocked all the time.”