Category Archives: management

JIRA is the baby version of Google Wave

Often the problem in development projects, especially those that involve many people and parties, is that a lot of the information and knowledge about current discussions and decisions is merely captured in emails. Emails, however, are merely chronological and often contain many strings of thought. New thoughts are copied into new emails with new mailing lists. Parallel communication takes place with different people. In the end, the aggregation of the insights is nearly impossible and individual employees need to be assigned to collecting and documenting this information again. This is clearly inefficient.

The advantage of Google Wave is that multiple people can work on one Wave about a single topic and do not need to order their discussion in chronological order. Additionally, a clear change history can be used to track changes – and more transparent than with emails. Another point is that the information is centrally hosted for everyone to see and edit. It’s not concealed in individual mailboxes.

These advantages can also be found in JIRA, an issue tracker I am currently working with again. While Google Wave is not available yet and will be mainly focused on non-business use, the advantages described above can already now be used with tools such as JIRA.

I do not want to be unfair to the brilliant work of the Google Wave developers. It’s preview promises far more: real-time collaboration, inclusion of maps, editable in real-time, a great user interface with a people-centered approach and much more. But at the same time it will not have workflows included – it is not designed as an issue tracker.

I would hope that the JIRA developers and the community around it takes notice of the great stuff Google is doing and takes some inspiration for their own roadmap. This would ease project and knowledge management greatly.

For more info on Google Wave you should really watch this video:

1 Comment

Filed under communication, Knowledge, management

The Difference Between Consultancies and New Media Agencies

Comparing consultancies and agencies, the first impression is that they are very similar, almost the same. But there are some crucial differences. Based on these differences, I will present some recommendations for new media agencies to reduce risks and maximize the ROI.

Starting with the similarities:

  • Both sell manpower and rely on the knowledge of their employees for quality in the work delivered.
  • Both are called-for when work needs to be done that the client’s workforce is not capable of doing or is understaffed to do so – additional staff won’t be hired for short-term products. 

Differences:

  • While consultancies mostly sell non-scalable amounts (working hours/days needed), the agency mostly sells outcomes (an end result of a project with a functionality) for a fixed price. Thus, agencies usually have a greater risk of not meeting time and budget, or the opposite may be true, generating a larger ROI than with the non-scalable work of a consultant. Agency work seems to be more risky, therefore.
  • Since agency work involves more repetitions than consultancies, standard tools or technologies can be developed or learned in order to cut on time and budget. If an agency manages to exploit this possibilty better than its competitors even with the expected personalization, it may reduce its costs, and thus, their profit margin. As soon as these tools develop to fully scalable products without need of real personalization, it can not be fully counted as an agency anymore but rather as a vendor which is not the focus of this blog.
  • The investment for receiving a job is considerably lower for a consultancy than for an agency. While it is sufficient for a consultancy to send consultant profiles to a (potential) client, that does not suffice for an agency to whin a pitch. A consultancy is usually confronted with a pitch that requires way more ressources than the adaption of existing consultant profiles. Often, weeks of man power are invested into concepts and presentations, not knowing whether the effort might be converted to sunk costs if the pitch is not won.
  • Consultancies are seen as partners, helping out during bad times, agencies are usually seen as mere executors that adhere to the wishes of the client. In combination with fixed price projects, this may be a very risky combination for the agencies if requirement management and change request management is not handled well. A client’s wishes are most often inprecise at the start of a project and equally as often undergo changes during the project (well known scope-creep). 
  • Consultancies are most often requested for work on subjects with high management attention, mostly concerning the core competencies. The objectivity of consultants is required to best evaluate the sharpness of the competitive edge. Agencies are usually summoned to execute projects that need to be done, but are not recurringly vital to the company – otherwise the client would have invested in employees that could do the same work. In rare cases that is not the case, but then the client is so dependent on external suppliers (in this case agencies) I would not recommend this approach to him.

All in all, I have painted a picture that clearly shows more risks for the agency’s business. What would I recommend to reduce these risks and maximize ROI? 

  • Requirements management, change request management and bid management need to be exceptionally well handled. The first two because that may reduce unexpected costs during the execution of a project, the latter may reduce sunk costs by either prioritizing bids well according to the probability of winning them or by improving the quality of the pitch material, thus improving the chances of winning.
  • Increasing the credibility and thus the trust with the potential client in order to increase the possibility of winning a pitch. Herein lies the power of communicating your knowledge openly and an increased brand recognition thereof. 
  • Constantly improving the tools you can use to minimize the costs while executing your project.
  • Selling more projects of a kind to reuse knowledge, leverage well functioning tools and routine, and thus increasing economies of scale
  • Selling more consultancy work as add-on to the mere execution of technological projects with a clearly defined output

Leave a comment

Filed under Knowledge, management, Reuse

Competency Deployment Needs Management Support

A prerequisite for value generation through knowledge is the proper identification of an employee’s comptetencies. However, this is only the first part of the deal. The actual deployment of these competencies can only be facilitated when the management is listening to the ideas of the employee and allows for changes. 

Any costs created by acquiring new and fresh competencies may be in vain when dreadlocked habits inhibit change and even ignore work already done. If the work is not leveraged due to a resistance toward the new approach, sunk costs are created. Additionally, frustration and demotivation might arise and inhibit further innovation introduced by the concerned or other new talents.

Leave a comment

Filed under Knowledge, management