If you read the previous lesson, you can probably guess what this one is about.
After we finished uploading all of the questions, answers, files and the rest of information related to each of the lessons, the next step had to be done. This was the task of retrieving every-single-little-file that was used to upload information. They wanted to have a backup of information.
David, Larry’s cousin, was in charge of this. This took him..well… I think that to this day (about four years later), he hasn’t finished retrieving the information and I doubt that he will get it anytime soon.
Obviously this was more than expected. It wasn’t so much the idea that he couldn’t FIND all the information, because all he had to do was ask which person uploaded this or that subject. That wasn’t it.
They wanted to backup ONLY the information that was uploaded. That was quite a task, because maybe someone uploaded 10 questions but changed half of them while he was uploading them because they had mistakes of context. Or some answers were changed because the teacher who uploaded them thought they were way too easy for a high-school level student.
The process was done with very little time and many people were involved, so mistakes were bound to show up sooner or later.
So, which questions were changed? Who had them? And could we be sure that the files they had matched exactly what we had uploaded? No one knew.
I think that, at the end, they simply decided to not get those files but simply copy and paste the information on the site to an independent file. Again, more extra work that wouldn’t be needed if they just organized properly. The teachers, obviously, had to do this tedious copy-and-paste work.
In short, we copied and pasted the files to the system. Then we copied and pasted information from the system, to individual files.
Long story short, one more time, a consequence- an avoidable consequence- of the continuous lack of organization.
“Mantener la calma durante una emergencia podría salvar vidas.
Antes de discutir lo que puedes hacer para mantener la calma y enfocarte durante una emergencia, les diré el motivo por el cual es importante mantenerse enfocado y tranquilo.
Cuando el organismo está bajo estrés, se activa el “modo supervivencia”, mejor conocido como “síndrome de pelear o volar”. Bajo estas condiciones, el cuerpo se prepara a sí mismo sobre-produciendo la hormona del estrés: cortisol. Después, el cortisol se dirige al cerebro ocasionando un retraso en el proceso de la corteza prefrontal, que es donde se genera el pensamiento crítico y es donde se localizan las funciones primordiales.
Por lo tanto, el capitán de “tu barco” ya no tiene control, y la amigdala de donde viene el síndrome de “pelear o volar” y donde se originan tus emociones, se hace más grande y toma control. Finalmente el hipocampo, que es donde se localiza la memoria y la habilidad de aprendizaje, se estrecha temporalmente.
Cuando te enfrentas a una emergencia, estás creado biológicamente para ser reactivo, en lugar de ser pensante o analizar tus pensamientos. Como resultado, el pánico te obliga a comportarte de manera emocional en lugar de racional, mientras reaccionas emocionalmente al peligro frente a ti.
Dado que ya no vives en una sociedad primitiva donde un comportamiento impulsivo y reactivo puede salvar tu vida, debes ajustar tu comportamiento de manera deliberada para adaptarse al riesgo y/o emergencia a la que te estás enfrentando. Y tendrás una gran desventaja cuando enfrentas una emergencia de manera emocional, en lugar de una manera lógica.
Por lo tanto, para mantener la calma frente al peligro, es importante no reaccionar y de forma consciente encontrar maneras para mantener la calma.
El autor Kevin Daum indica que los pilotos de carreras tienen un dicho: “Despacio en la cabina significa rápido en la pista”. Recuerda las tareas importantes de sobrevivencia, como llamar al número de emergencias, dejar de sangrar, o dar Resucitación Cardiopulmonar, requieren que mantengas la calma.
Los niños toman indicios de sus padres: si mantienes la calma, suavizas el pánico en general.”
Esta es una traducción de un fragmento de un artículo en Inglés.
Si te interesa leer el artículo completo, visita
At this time I honestly don’t know exactly what the lesson is, but I figure that as a write, the idea will come to me.
When we had finished recording high school level, it was time to upload the activities that were related to each lesson. They consisted of a Blog entry, some questions about that blog entry, interactive activities, an exam at the end of the lesson and frequently asked questions.
We had to manually upload every single letter of those activities. They hadn’t developed a way to automatically upload this information (they still haven’t). Also, we had a system that didn’t allow right-clic options. So we had to manually select a piece of text, type Ctrl-C, then go to the system window and Ctrl-V the information on to it.
This was very tedious work. Imagine having to copy and paste 25 questions, then their possible answers (3 at least) for 30 something lessons. Then frequently asked questions were about 5 per lesson (times 30 as well). In short, it was quite a lot of information to copy and paste manually.
And, as always, they wanted this done yesterday. So, their idea to get this done quickly? Everyone do it.
We divided the work. Or distributed rather. One person got 5 exams to upload and someone else got 10 exams of that same subject.
In this way, one subject was being managed by two or three people at the same time.
And it was done like that, no questions asked, just upload everything as quickly as you can. Of course, something done in haste has a high chance of resulting with poor quality.
And it did.
Files got lost and there were many mistakes made. If a physics teacher was uploading a History test, it would have been difficult for him to spot a mistake in context or an important date. The same happend with biology teachers that uploaded information for math or calculus.
It got done quickly, yes. But at the cost of quality. To this day I still don’t understand why that had to be done so quickly, since there weren’t any students enrolled. One might think that they wanted to save expenses, but the difference in doing it with more care would have been a couple of days. Maybe a week.
And we ended up re-doing this a few months later, when there wasn’t much to do. Maybe this was their plan all along, to do the exact same thing two times.
So what was the point of doing everything in a hurry? Just the fact of being able to say ‘it’s done’ (even if we don’t know what the hell we uploaded because there were so many people involved in the process). Again, the lack of organization was evident.
Therefore, one more time: organize, organize, organize. That is the lesson. Even if we had to do something quickly, nothing would have happened if we had taken a couple of hours trying to figure out the best way to get the work done.
A two hour salary of three or four people is much cheaper than the salary of 15 people during three weeks. So spend some time planning and figuring out WHAT you need to get done and HOW to do it. Also consider the possible implications or consequences. This alone can save a few headaches. Then go ahead and act.
What came next could be the only outcome of this lack of vision.
Next: Dude, where’s my file?
No, this one doesn’t talk about anyone winning at anything.
The winner was simply the first person to get to the office. We had a bout 20-something computers.
The concept was ‘first come-first serve’. If you got to the office at, say 7:55 you had 20 computers to choose from. You could sit anywhere you wanted. The later you arrived, the fewer computers that were available. No one had a place assigned, except, of course the big shots like Larry, Mathew and Sam. They had their own private office.
For some reason they didn’t want to assign a space to their employees. Why? Because that way all of the computers are “for everybody”. Nobody “owns” a computer, so to speak. So everyday, we arrived and we didn’t really KNOW where we would work that day. So if I had worked on a couple of files the day before, I would have to save them to a flash drive, a portable hard drive or upload it somewhere because I wasn’t sure that I would be able to use the same computer the next day.
You can imagine the implications of this. Computers often got viruses and had performance issues. Files often got lost or corrupted. If someone saved their work in one computer and the next day someone else was sitting there, they had to “borrow” the computer for a while so that the files could be retreived and work could continue. Just writing this now, gives me a hint of a headache.
But that was the way these guys had designed the working-system. If it can be called as such.
There was this guy, Larry’s cousin, who I will call David. David was in charge of tech support. He was the ‘computer guy’. And he had A LOT of work to do when we worked like this. He used to format computers almost on a daily basis (I wonder why). And when he asked what was done in the computer or when he tried to figure out what was wrong with it, he had a hard time. Because he couldn’t find out exactly who had used it or who had done what with it.
This continued for like, the first year or so. Everybody had problems with the computers. They often had viruses, which was the most common problem. Then when new teachers were hired, we began to run out of computers. So there were times when people arrived and found out that there were no machines available.
So Larry lent them his own laptop. How do you hire someone and not take into account that you don’t have enough work stations?
They bought like two laptops to lend when this issue arised. It seemed easier than assigning specific work stations to teachers. At least, it seemed like that.
And people complained and got ignored and we kept working like this for quite sometime.
This time, it feels obvious enough to say that your company should look for practical solutions and simple ways of organizing. But, after this little incident, I can’t stress this enough.
The lesson this time is this: think simple.
In this case, it would have been A LOT easier to just assign a workstation to each teacher. John, your machine is number 1, Frank-yours is number 2, Helen-you’ll take number 3 and so on.
This way, everyone had their files on their own machine. No files would be lost. Or at least the possibility of them getting lost would have been scarce. If everyone wasn’t putting their flash drives on every computer, viruses would be avoided.
Well, they came to this predicament about a year after starting the business. And we have worked like this ever since. Why didn’t they do this before? I don’t know. Apparently, things get done when Larry says, not when it is needed.
So think practical, easy, simple. If it seems too complicated, it probably is. And employees will have headaches trying to work like that. Problems will eventually present themselves and you will have to deal with them. This will cost you time and money.
Some problems can be foreseen or prevented. But others show up much later. We really can’t do much with unexpected conditions, except work them out as they arrive. But we CAN prevent easily identifiable problems using common sense.
Wheter it’s organizing a recording session, assigning a work station or figuring out what the next step in your venture should be, apply the KISS principle: Keep it simple, stupid.
Don’t believe me? Check these out:
Next: Army ants.
Inside the world of ”lesson recording’, there was a little character widely referred to as pure evil.
I will, obviously change the name of this software so I don’t give away the company and people that are involved in this little writing exercise. Let’s name it ‘the grape’, because it kind of sounds like that in my native language.
I am going to get a bit technical to make my point, so bear with me.
All the lessons were designed in one of the most widely used software for presentations. Yes, you got it, that’s the one. We designed one file with picture slides, information slides, examples and so on. And we would design another slide show where we would write everything we would say while recording. A.k.a. our script. They believed that we should not improvise when recording, because we weren’t actors. And I think they were right. So we simply wrote everything down and we just read in front of the camera. Kind of like a tele-prompter.
So we had two presentations. When we got to the recording set, we had to work with a recording program. And we had another little program called ‘the grape’ to link both presentations and the video recording program. With these four programs, we would use a remote control to tell the computer when we wanted to show ourselves on screen, then switch to the slide, then combine teacher and slide at the same time, then back to the slide, then just the teacher and so on.
With the remote, we wouldn’t need a camera man. Just the teacher, controlling the slide show, camera and everything.
But there was a catch: the grape program was extremely complicated to learn and even more complicated to make changes if you made a mistake while recording. This program was designed and written by the main engineer of this whole operation, the right hand man of Mr.Gestures, Todd, or Mr.T.
This guy was the author of the software that linked everything inside the set and he was quite selfish about it. The only computers that had the software installed were those inside each set.
When we had to record a lesson, what teachers had to do was take all their files to the set. Then, we had to painstakingly build a sequence in which we told the computer which slide would go first, then just show what the camera sees, then show the teacher and the slide at the same time, then go back to just the slide, then advance my script, then advance the slide…you get the idea.
This program simply recorded steps. Each step would tell the computer to switch from program to program. The concept was simple, but the average slideshows had around 80 slides, not counting animation effects. Yes, each clic was considered an additional step.
So we would have to make 150 or 200 steps per sequence, one by one. Maybe even more. And we did this for each lesson.
Not only that, when we were done with the sequence, we used to run it BEFORE recording, to check for mistakes. If a mistake was made or something was not working properly, we had to look for the mistake manually. This meant that we would have to check every single little step of the process, to find out where the mistake was.
When it finally worked, we would record the lesson, save it on the computer and continue with the next one.
When high-school was being recorded, some teachers cried because of the frustration of not being able to make the program do what they needed. Others banged on the walls to show their anger. It was definitely not pretty.
When junior-high was recorded, we didn’t have as much trouble because we had some experience. But the new teachers had to experience the same frustration that we did.
Luckily for them, the five supervisors in charge of each area had already recorded some lessons and were able to give some tips and suggestions for the newcomers. This aliviated the frustration, although not entirely.
Imagine analyzing each clic, step by step, around 12o of them per lesson. And each subject had around 40-something lessons. You do the math, it was very tedious work. Also, we had to do it in a tight schedule because editing was waiting for us and they wanted to send out the product in order to get students enrolled by the government.
The process improved somewhat, but not enough. What could we have done differently?
Well, we could have gotten rid of that damn ‘grape’ program. Nobody actually thought about the efficiency of using it or if there was an easier, quicker way of designing that sequence. It was Todd’s masterpiece so, why would we dare try to change it or use something else to record?
But the point is that if something seems too complicated or it’s taking too much time to do., if you are constantly getting frustrated about how you are doing something, then you are probably not doing it right. Too many frustrated teachers should have been a sign to come up with a better way of recording.
Eventually, some teachers who specialized in computer science and programming came up with an idea to make the program work more efficiently. But they did this in their own time, out of compassion for their fellow co-workers.
So here is the lesson:
If you are the boss at a startup or any work environment, make a habit of talking with your employees. Find out what their needs are, search for ways to make their work more efficient, less tedious, easier and faster. How can you improve something if you don’t even know what you produce or how you go about making it a reality?
The guy that designed this little gem never actually recorded any lessons. So it was doubtful that he could really understand how things developed inside a recording set. The general rule for new teachers was just “you’ll get the hang of it eventually, don’t despair”
The owner, obviously didn’t know that this was happening, either. He rarely stopped by to see what was going on.
And when he did, he just went into Larry’s office and asked him how things were going. And it was kind of interesting to know how the owner, the guy providing the payroll, only bothered to ask Larry. The only guy who didn’t design lessons, didn’t record and didn’t really know how the production process worked.
So, get involved with your company. Get your hands dirty, investigate, ask around, evaluate how work gets done. Then come up with ways to improve that. Your employees will appreciate it quite a lot. And everyone knows that happy employees are employees that work efficiently and tend to stay with the company.
Next: Winner take all
After failing at improving the work schedule, I decided to keep doing what I was doing and just comply with whatever I was told to do.
Even though a lot of us told the people at the top that professional level courses were the way to go, Mr. Gestures had a meeting with the government and had agreed to finance a junior-high level studies virtual course and forget about professional training. At least for the moment.
So all of the teachers focused on that.
I am trained as an architect so I was somewhat surprised when they gave me the subject of Geography. They said it was the subject that I was best suited for. Might I add that History and Geography were not my favorite subjects in school, but I had to do it, so I did. It came out pretty good, actually. It is still online, to this day- I think.
The interesting part of this anecdote is the moment when we had to record the lessons. Junior high had about a thousand virtual classes. There were around 14 teachers designing lessons. We all had to record them. There were 5 recording sets available.
The high-school recording sessions were a mess. We took around two or three months to record. Maybe a little more. No one knew where you had to record, which set was available or how much time you had to work in there.
Most of us thought that it would take almost the same time to record junior high, if not more. But, in this case, the person in charge was a female teacher by the name of Helen. Yes, Helen, that’s the name I will give her. She was and still is, quite responsible and organized.
I don’t know if gender has anything to do with it, but most of my male-bosses have usually been disorganized. The only female boss I had ever had was a principal and she was very organized as well. This time, Helen was partly in charge of junior-high and she came up with a simple schedule for the recording of the lessons. Some of the teachers helped her a little in elaborating it.
She gave each of the teachers a schedule in a printed sheet, which included the set number, the time and the names of each teacher. This way, I knew exactly at what time I had to record and in exactly which set. It was simple, but very efficient.
At the moment, I designed the Geography subject and I also had to check the work of three other teachers that were designing lessons about computer class (referred to as technology subjects)
There were 5 people in charge of each area: science, math, technology, social studies and spanish. They named us ‘supervisors’. I was one of them. And Helen was in charge of us. And Larry in charge of Helen.
Well, when we were figuring out how to record, Larry suggested that-while the recording sessions were taking place-ALL of the supervisors be here ALL day, to be available if any teacher needed help recording. He wanted us to arrive at 8 a.m., leave at 12 o’clock and come back at 4 p.m. and leave at 8 p.m. There were going to be teachers recording all day, so we needed someone available for technical help and to check that teachers got in on time and in the right set.
But this made no sense to us. Who would be available from 12 pm to 4pm? We even had a meeting to discuss this. A very long meeting- which was the protocol for the meetings: long hours, little or no decisions made. But Larry insisted that it was mandatory for ALL of us to be here.
So, when the meeting ended, the supervisors got together and -in 5 minutes- determined that we should take turns. There were five of us, so each had to come back in the afternoon only ONE day per week. In short, it was more organized and it made more sense. Most teachers had trouble recording on the first day. But after that, they got the hang of it and recorded practically by themselves. So, five people standing outside of the sets, all day, was not necessary. We simply matched our schedule with the teachers that would be recording, so each supervisor would be available for their teachers.
The result: junior-high got recorded in a record time of between three and four weeks. As expected, Larry wasn’t pleased and couldn’t understand why we disobeyed him. And, to this day, he refers to the incident as ‘the day when you ignored my decision’.
Something else that is important to mention is that the teachers recorded relaxed, with a better attitude, looked better in front of the camera and produced a quality product. How was this possible?
We managed to do it with this lesson: organization is very, very important. Analyze the resources that are available. Write down stuff, make diagramas, have productive meetings and determine more than one way to get something done. Then evaluate pros and cons to take the best decision.
In this case, Larry didn’t agree with the way we did the recordings. But he didn’t suggest any other way to do it better. His attitude is and always has been “my way or the highway.”
Oh, as an added bonus, here is what Helen got in exchange for her outstanding work: a swift kick in the groin, so to speak.
Let me explain.
Several days later, after junior high was finished, Mr.Gestures came over. He wasn’t here everyday. But he came over and asked about who was responsible for junior high, because they needed to attend a meeting at the government offices where the school’s permit was being processed.
Larry, obviously didn’t give any credit to Helen. He only stated that ‘we managed to get junior high recorded in record time’. Mr. Gestures didn’t ask any more questions.
When they were leaving for the meeting, we found out that Helen was never really in charge of junior high. It was just for ‘production’ purposes. Because the ‘real’ principal, was Mathew. Apparently, Mr. Gestures didn’t want any women in his meetings because ‘he wouldn’t be able to speak with his fowl language’ i,e. swearing.
For your information, Mr. Gestures was not offensive, but he did swear. A LOT. He didn’t exactly use the vocabulary of a professional engineer, which is his professional training.
Anyway, Helen was very upset about this. However, she simply said quietly and modestly to herself ‘oh well, I know that I am in part responsible for this success, no matter what they say'”. And everybody else knew that without her guidance, we couldn’t have done it so effectively.
Next: Lesson 9-Headaches make people cry.