Playing for Real: Getting Started

By the time I pulled back into the parking lot after lunch at home, I knew something was wrong. The first sign was the ambulance racing out towards the hospital with full lights and sirens. The second sign was catching a glimpse of the crowd of guests on the bridge slowly walking back in the direction of the pool. You can’t see the pool from the parking lot, but it was obvious it had been cleared. While we would empty the pool every couple of weeks on a lost child search, the combination of an empty pool and ambulance didn’t bode well. But accidents happen, this wasn’t the first ambulance we’d called, and as I exited my car and started towards the entrance I was more excited than anything else; wanting to know what I missed. It was only when I saw the faces of my coworkers and the guests as I walked in that I realized something terrible had happened. A kid died in our pool. Every now and then we have moments in our lives where disparate events coalesce into a coherent inspiration. Recently, I’ve been thinking a lot about my life in emergency services. A month ago I had to take an EMT refresher class to transfer my certification from Colorado to Arizona. Two weeks ago I gave a presentation on “The Firefighter’s Guide to Risk Management”, where I played off my past as a rescue worker to talk about Enterprise Risk Management concepts. Last week I finished reading “Playing for Real: Stories from Rocky Mountain Rescue”, an excellent book by Mark Scott-Nash, a friend from Rocky Mountain Rescue. Those three events made me realize how incredibly lucky I’ve been to have some amazing opportunities and experiences. For nearly 20 years now I’ve bounced around nearly every rescue job in the books- some paid, some volunteer, all professional. I’ve driven fire trucks, worked the ambulance in the inner city, flown on helicopters, patrolled one of the top ski resorts in the US, responded to Katrina, started IVs while hanging off cliff faces, SCUBA dived for bodies, and spent thousands of hours training for nearly any possible crisis. All of these adventures started in high school with my first non-fast-food job. Graydon pool is a mix between a man-made lake and municipal pool located in the New York suburb of Ridgewood, New Jersey. About 100 yards on each side in a vaguely rectangular shape, its sandy bottom is surrounded by an artificial beach. Originally a small pond, it was later excavated to its current size and massive filtration systems added. Visibility is still a pond-like few feet and we’d regularly row around in a small boat to drop chlorine tablets and other chemicals to keep it sanitary. A long buoy line snakes through the middle dividing the 0-4 foot deep shallow end from the 13+ foot deep end, equipped with a high dive, two concrete resting platforms, and a small lap area. During summers Graydon is the social center for Ridgewood. On a sunny day about a dozen lifeguards perched on 7 foot stands would watch over hundreds of swimmers of all ages. I was 17 when I started working there as a lifeguard and couldn’t imagine a better job. The pay was good ($35 a day my first year), the nightly parties better (thanks to a mix of high school and college-age staff), and at times I felt more like a professional volleyball player than a public servant. I can’t remember exactly when the drowning occurred, but think it was either in 1988 or 1989. Graydon was often the host for youth groups from other towns looking for a change from the traditional lap pool. I think the group that day was from Patterson, a low-income town whose school was featured in the film Stand by Me. While I was out at lunch a group of kids jumped off the main platform in the deep end, and started swimming about 30 yards towards the concrete T-shaped dock that held the olympic-height low and high diving boards. Once they hit the other side, they realized one of their friends hadn’t made it and quickly notified the guard at the diving area. I’m bad with names, and this was nearly 20 years ago, so while I remember what she looked like I can’t remember my coworker’s name. She was one of the few employees over 21 (that’s the kind of thing a 17 year old remembers) and on summer break from college. She immediately blew three short blasts on her whistle- the emergency signal for a rescue- and dove into the pool. Off-duty lifeguards would swarm over the area as everyone in stands would start clearing the entire pool. When enough guards hit the water in that area, we’d switch from a spot search to a more organized sweep that I later realized resembles an avalanche search. Side by side, the lifeguards would tread water in a line, dive to the 13-foot bottom, swim forward a few strokes, and start all over again. If we didn’t have a search area, or enough time passed, we’d grab SCUBA tanks, lay a few search lines, and start a dive search. Not that any of us were even certified to dive. But based on what others later told me the search never got to that point. Another female guard, in the next stand over, jumped in to assist and they quickly located the boy. Piecing the story together, he’d quietly slipped under the water without a struggle while swimming across with his friends. The two female guards found him very quickly and started mouth to mouth while swimming him to shore for CPR and to transfer him to the ambulance for a short trip to the Valley Hospital Emergency Room. That boy, high school at the oldest, never came back. The two guards were emotionally devastated and the death was a pall over the entire staff. Initially there was a suspicion that his heart stopped

Read Post

Totally Transparent Research is the embodiment of how we work at Securosis. It’s our core operating philosophy, our research policy, and a specific process. We initially developed it to help maintain objectivity while producing licensed research, but its benefits extend to all aspects of our business.

Going beyond Open Source Research, and a far cry from the traditional syndicated research model, we think it’s the best way to produce independent, objective, quality research.

Here’s how it works:

  • Content is developed ‘live’ on the blog. Primary research is generally released in pieces, as a series of posts, so we can digest and integrate feedback, making the end results much stronger than traditional “ivory tower” research.
  • Comments are enabled for posts. All comments are kept except for spam, personal insults of a clearly inflammatory nature, and completely off-topic content that distracts from the discussion. We welcome comments critical of the work, even if somewhat insulting to the authors. Really.
  • Anyone can comment, and no registration is required. Vendors or consultants with a relevant product or offering must properly identify themselves. While their comments won’t be deleted, the writer/moderator will “call out”, identify, and possibly ridicule vendors who fail to do so.
  • Vendors considering licensing the content are welcome to provide feedback, but it must be posted in the comments - just like everyone else. There is no back channel influence on the research findings or posts.
    Analysts must reply to comments and defend the research position, or agree to modify the content.
  • At the end of the post series, the analyst compiles the posts into a paper, presentation, or other delivery vehicle. Public comments/input factors into the research, where appropriate.
  • If the research is distributed as a paper, significant commenters/contributors are acknowledged in the opening of the report. If they did not post their real names, handles used for comments are listed. Commenters do not retain any rights to the report, but their contributions will be recognized.
  • All primary research will be released under a Creative Commons license. The current license is Non-Commercial, Attribution. The analyst, at their discretion, may add a Derivative Works or Share Alike condition.
  • Securosis primary research does not discuss specific vendors or specific products/offerings, unless used to provide context, contrast or to make a point (which is very very rare).
    Although quotes from published primary research (and published primary research only) may be used in press releases, said quotes may never mention a specific vendor, even if the vendor is mentioned in the source report. Securosis must approve any quote to appear in any vendor marketing collateral.
  • Final primary research will be posted on the blog with open comments.
  • Research will be updated periodically to reflect market realities, based on the discretion of the primary analyst. Updated research will be dated and given a version number.
    For research that cannot be developed using this model, such as complex principles or models that are unsuited for a series of blog posts, the content will be chunked up and posted at or before release of the paper to solicit public feedback, and provide an open venue for comments and criticisms.
  • In rare cases Securosis may write papers outside of the primary research agenda, but only if the end result can be non-biased and valuable to the user community to supplement industry-wide efforts or advances. A “Radically Transparent Research” process will be followed in developing these papers, where absolutely all materials are public at all stages of development, including communications (email, call notes).
    Only the free primary research released on our site can be licensed. We will not accept licensing fees on research we charge users to access.
  • All licensed research will be clearly labeled with the licensees. No licensed research will be released without indicating the sources of licensing fees. Again, there will be no back channel influence. We’re open and transparent about our revenue sources.

In essence, we develop all of our research out in the open, and not only seek public comments, but keep those comments indefinitely as a record of the research creation process. If you believe we are biased or not doing our homework, you can call us out on it and it will be there in the record. Our philosophy involves cracking open the research process, and using our readers to eliminate bias and enhance the quality of the work.

On the back end, here’s how we handle this approach with licensees:

  • Licensees may propose paper topics. The topic may be accepted if it is consistent with the Securosis research agenda and goals, but only if it can be covered without bias and will be valuable to the end user community.
  • Analysts produce research according to their own research agendas, and may offer licensing under the same objectivity requirements.
  • The potential licensee will be provided an outline of our research positions and the potential research product so they can determine if it is likely to meet their objectives.
  • Once the licensee agrees, development of the primary research content begins, following the Totally Transparent Research process as outlined above. At this point, there is no money exchanged.
  • Upon completion of the paper, the licensee will receive a release candidate to determine whether the final result still meets their needs.
  • If the content does not meet their needs, the licensee is not required to pay, and the research will be released without licensing or with alternate licensees.
  • Licensees may host and reuse the content for the length of the license (typically one year). This includes placing the content behind a registration process, posting on white paper networks, or translation into other languages. The research will always be hosted at Securosis for free without registration.

Here is the language we currently place in our research project agreements:

Content will be created independently of LICENSEE with no obligations for payment. Once content is complete, LICENSEE will have a 3 day review period to determine if the content meets corporate objectives. If the content is unsuitable, LICENSEE will not be obligated for any payment and Securosis is free to distribute the whitepaper without branding or with alternate licensees, and will not complete any associated webcasts for the declining LICENSEE. Content licensing, webcasts and payment are contingent on the content being acceptable to LICENSEE. This maintains objectivity while limiting the risk to LICENSEE. Securosis maintains all rights to the content and to include Securosis branding in addition to any licensee branding.

Even this process itself is open to criticism. If you have questions or comments, you can email us or comment on the blog.