CCP Communication

I spent the first five years of my professional career out of college working as a consultant for small and medium sized business in the IT world in Chicago. At that job I learned a number of important business rules. One of them was boiled down to a single phrase that the CEO said to me during my first month – perception matters.

In the client’s eyes, it is not so much that a problem has occurred; there will always be problems and obstacles to work around. It doesn’t matter if you reformatted the server, lost an email, or simply forgot. What matters is what you are aware, working on it, and that this message is effectively and clearly communicated.

I toughly enjoy reading CCP’s Devblogs as they give me warm and fuzzy feelings.  I am the eager client awaiting the new item and the Devblogs placate me.

In CPP Sreegs’ latest Devblog, New Forum Security Blog – Cookie Derp, the highly public facing issue of the new forums’ security measures were addressed: Yes, there were oversights. Yes, there was a breakdown of internal QA processes. Yes, there was mismanagement of resources. They are working on it and we have to wait. I would much rather know the details of the situation as outlined in the Devlog than be told that there simply ‘was an issue’. For this type of transparent client communication I am grateful.

I understand that many people are citing this as another one of CCP’s 80% implemented deliveries. I am also starting to notice these trends (or perhaps I am becoming a bitter vet) but you know what? I still subscribe, I still am involved in the community, and I am looking forward towards the next series of expansions.