Fire Drill Template: Fill & Download for Free

Behold:1)The kid who broke a window with his sweaty shirt after flinging said shirt into a fan, which proceeded to fling shirt into window.2)The kid who lost his test paper out the window3)The kid who ran into some clearly visible string which was being used as a marker and almost decapitated himself (I may be exaggerating here)4)The kid who almost fell out of the window while looking for a correction tape he INTENTIONALLY threw out.5)The kid who managed to stab his friend with a broken broom (yes I know it's hard to believe) after having a "fake sword fight"6)The kid who put a banana in the flame of a Bunsen burner. Discovered when the banana caramelised and the teacher suspected someone was eating in class.7)Same kid in 6 who put a)a cabbage, b)copper sulfate and c)a test tube holder into said Bunsen burner.8)Same kid in 6 and 7 who threw his correction tape into the fan and asked me to recover it. And yes, it was tangled badly. And he did it again twice.I guess that's all… OH WAIT9) Me, who burnt all the hair off his fingers after failing to light up a Bunsen burner before a large gas cloud has accumulated.Now the list is complete.Edit: 10)The kid who threw a chair at me because I asked him to move his table to the back because everyone was waiting for him. His excuse? I "was rushing him".11)The kid in 10) a)broke a fan speed control(the knob with 0,1,2,3 on it), b)says "no u" to everything (e.g. "What would you like to eat for lunch?" "No u")c)screams random German words in class, which are out of context and annoying. Not my opinion, everyone's. d) very proudly posted a video of himself on instagram lighting 50 matches in a rubber band, despite the fact that he damn near burned his house down.12) The kid who sprayed the history teacher with deodorant and was promptly punished.13) Not my school, but a kid broke a window with a jackfruit.14) During an outdoor camp, the kid who inflated the kayak for my friend and I forgot to plug the inflation hole and nearly sunk us both.Edit 2:15) A kid in my Chinese cultural class, which was mask painting, painted said mask completely black with red lips. It's supposed to be colourful and the teacher told us to paint according to a template.16) In my previous school, a kid fell in the school pond. When someone tried to help him, the Good Samaritan was pulled in due to the guy's weight. Another one who tried to help also fell in.17) In my classmate's previous school, a kid threw his bag out the window during a fire drill because he thought it was a real fire. Said bag hit a teacher.18) My classmate who shouted "f***" for comedic effect before apparently realising that a) the teacher was in class and b) the teacher has ears.19) In my previous school, a kid bought a lighter from a small shop and proceeded to pick up a used cigarette from the floor and smoke it, and then proceeded to set fire to a packet of oreos. Oh, and he did this RIGHT IN FRONT OF THE SCHOOL.Edit for even more hilarity:20) A kid tried to jack off in a tuba. What. The. Heck.21) A kid raised his hand during St. John's ambulance brigade practice and said to his sergeant: "Sergeant, I'm horny!" Thinking that this was just a joke, the sergeant said back:" I'll give you ten minutes to [insert term that means something i'd rather not write]" He sat in front of the flagpole and actually did that act.22) Some geniuses thought it'd be an absolutely wonderful idea to jump over three chairs. As I walked out of sight of the scene, I heard a loud crash and screaming.23) I'm in fencing. I broke a light in the fencing hall. Enough said.24) Some intellectual decided to shout "OMG you f*****g idiot" at the top of his lungs in front of the principal and 10 teachers.25) A kid in my previous school tried to slide across the polished floor and proceeded to launch himself down a flight of stairs.26) A kid in my previous school was giving a speech. He couldn't get the microphone to work and swore. Guess what? The microphone broadcasted his profanity to the entire hall.27) My classmate tried to open a can of sausage and managed to slice his thumb open.28) My classmate tried to cut an apple ON HIS HAND and promptly stabbed himself.Don't worry, they're fine.

Yes, I believe so. This is because it helps you understand the attitude of people when it comes to any type of organizational change and how to communicate better with people. This will certainly help you when applying for jobs in this field.Change management training is a lot like practicing fire drills but without the loud noise. About 70% of change initiatives fail, which makes cultivating change management skills so important.Here are 5 important ways of how you can be benefited by Change Management Certification.1.Gain a structured approach:Certification provides a clear, formalized methodology and process for doing change management.It also provides a structured way of thinking and deepens your understanding of the dynamics of change.2. Build skills and credentials:Certification increases professional credibility and is an important step for advancing your career.Certification also builds confidence in your ability to succeed at change management.3. Acquire tools and techniques:Certification provides tools, templates, techniques and exposure to methodologies, common practices, language and frameworks that you can immediately apply to change projects.4. Your knowledge and expertise are validated:With a certification, your position as a leader of change is authenticated, making it easier to gain sponsorship from leadership and employee buy-in, lowering the overall resistance to change.5. Can achieve desired outcomes:Participants felt that by attending certification, they were more able to help their organizations recognize the value of change management and assist them in creating a standardized approach to managing the change that increased proficiency and the likelihood of achieving desired outcomes.Understanding these benefits and the value prior to signing up for certification is important to ensure that you get the most out of the course and that you actually enjoy it!How much the Change Management Certification will cost? Know the price!

I support the general approach, but am suspicious of any arbitrary metric (e.g. 2%). First, some reasons to completely pull out features that are not being used very much:- UI overhead. If you have a product crammed full of obscure and lightly related features, your users will necessarily have trouble finding / using / remembering those features. More importantly, the "happy path" or dominant use patterns will be incrementally clogged with options or choices that don't matter. UX/UI leads (and product managers) should be pushing for yoru product to do its core job as simply as possible, with least number of steps/complications.Our counter-example is any product within Microsoft Office. After a few decades of feature accretion, it's increasingly hard to get anything done. Ribbons? Modal boxes? Drop-downs? Where is that widget I need to change the selection range on my pivot table? How do I apply this PPT template to that presentation? I suspect that 70% of Office's features are rarely-if-ever used yet set my teeth on edge...- code overhead. If you build commercial software, you have some reasonable obligations to know it works and rigorously test each build. So an unused feature with 1000 lines of code requires a few dozen automated tests, some dev time for periodic bug fixesor refactoring, platform support, etc, etc, etc. You're deluded if you thing that last year's (purportedly) working code will magically keep working this year. Most expensive resource: someone on your dev team who is supposed to remember how this works, be available to traige problem reports, and drop what she's doing on strategic code to "just fix this one little thing that shouldn't take more than 15 minutes."- customer confusion. You're inviting some small set of your users to think of this product as primarily intended for some obscure secondary purpose. E.g. if your file backup utility includes a spell checker function, you're inviting customers to make it their edit-and-backup-at-the-same-time utility of choice. Expect a stream of enhancement requests from publishers who want foreign language spell-checking options, now that you've pointed the way... This might be a great time to decide if you want to be in the stand-alone spell checker market.- tech support burden. No one gets good at using rarely used features. Tech support forgets about it, documentation writers side past it, user forums never mention it. When an actual user tries it out (and fails), an entirely expected fire drills results. Or your user shakes his head, gives up, and thinks badly of you.- missed opportunity for an Engineering celebration. Your dev team would probably love a chance to retire some bad old code, both for rational reasons above and because it feels good. Toss out the cruft! Streamline the build! Bury the code so we don't have to support it any more! As a product manager, you have a wonderful opportunity to applaud good code hygiene and debris removal. Don't forget to bring pizza.- own your decisions, force clearer thinking. Here's your moment of humility by saying this outloud to your peers and dev team: "I included this in an earlier user story/MRD/requirement, but I didn't get it right. I own that decision. Subsequent events, market changes or fresh experience convince me we should pull this feature out." A good reminder to ask for features that you think really WILL matter, deserve to be built, have strong justification. Hate the feature, love the learning. Lead with intellectual honesty.BTW, I'm suspicious of the 2% boundary. Situations I'd be wary of:- this is a rarely used but strategic feature, e.g. "convert data from our hated competitor's format to our format so we can steal away their key accounts." Used 3x per year, but is occasionally heroic.- this is a checklist feature that absolutely no one uses, but appears often on government RFPs. You'll be excluded from selling any products to NATO unless you claim a currency symbol configuration option. :-)We should thing about our products (services) as doing a specific job well for our customers. Barnacle-covered products which are harder to use -- and doo too many things badly -- don't serve well. Try to keep focus on what your product should REALLY be doing, and focus there. Ripping out some bad old features is a nice way to reinforce that.