Securosis

Research

Announcing the CloudSLAW Patreon!

TL;DR: Support CloudSLAW Here! I know that as most of you lay your weary heads to rest every night (or morning, for you night shifters), the last thought that fires through your synapses is, “I really wish I could get more CloudSLAW!” Well, now you can! I’ve been debating for a while on the best way to keep this crazy thing going. With over a year of content and nearly 60 labs, it’s time to take things to the next level, and set this project up for longevity. Each 15-30 minute lab takes me about 5-8 hours to produce, and that number is only going up as we get into more advanced content. Plus there are various tool and hosting costs. I’m not complaining — it’s what I signed up for — but it would also be nice to cover the costs. And if things blow up enough I’ll be able to get a little support. My first goal would be to get some video editing help to speed up that part of the process. Second I’d like to hire someone to help maintain the older labs with screenshot updates. I’m sure some of you noticed that AWS rolled out a user interface update a couple months ago, so now all the square buttons are… less square, and sometimes different colors. It sure would be nice to have those updated, and at some point even deeper changes will hit. This is where the Patreon comes in. It’s an opportunity to support the project and get a little extra in return. To be clear, CloudSLAW itself isn’t changing and everything is still free — this is all just an add-on. We have two tiers: CloudSLAW Pro The Pro tier is all about extras to help you learn even more. For $10 a month you get to support the project and: Gain access to our lab support and community Discord. Where I’ll probably be hanging out… more than I should. I’ll hold weekly official office hours when I’ll be online to answer questions and help with any lab issues. We’ll even pop open a screen share if needed. (Note that this is most weeks — sometimes I travel or vacation). Access to periodic subscriber-only webinars. These will be live, and I’m shooting for roughly monthly. Some will be presentations I’ve given at conferences, and others will be CloudSLAW-specific. For the first one I’ll walk through the current lab block on Advanced Cloud Problem Solving and talk in more depth on the architecture and decision-making behind it. Access to previous webinars. It turns out you can record them! You’ll get to propose and vote on future labs! There are a zillion directions where I can take this, and Pro members will help steer content. To put things in perspective, baseline pricing for most of my trainings ranges from $1600-$4500 for classes which are 2-3 days long. This is relatively standard for live technical training. I’ve always been a little uncomfortable asking individuals for money, but these are all purely optional add-ons, and they will help me keep producing the core content for free. CloudSLAW Tipper $2 per month just because you like me, and you don’t get anything in return except for warm fuzzies. Not everyone wants or needs the Pro benefits, so this is just a way to let me know you really care. 😀 Thank you for reading and considering! Sign up for the Patreon Here! Share:

Share:
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.