Skip to main content

Pointless meeings

I often get grouchy at meetings. Often meetings are held for the sake of themselves. Sometimes you have meetings where you have a good purpose, but they don't lead to anything. You have all been on these pointless meetings. In these meetings you do not know what to say and often it is the same for everyone. Everyone tries to say wise things, but it's like trampling water, instead of getting somewhere

You sit there and everyone talks about the problem instead of the solution. Do you listen to what people say you hear:


  • Unspecified noun ("We" - Who we? "Help" - What help?)
  • Unspecified verbs ("engages us" - in what way? How?)
  • Generalizations (all, nobody, always, never)
  • Rules (must, can not)
  • Comparisons (better than, worse than)
  • The participants repeat the same thing over and over again

This is a symptom that the discussion does not solve the concrete problem.

What we have to do is look for alternative methods to tackle the problem instead of talking about it.

What? How? When?

The key questions for solving a problem are:

  • What is the problem?
  • How can it be solved?
  • When can I start?

First, you have to agree what the problem is. Just through a good problem formulation, you often see the solution. I don't know how many times I've been in a situation where a person has started to ask a question and by having to formulate the question also found the answer.

Once the problem is formulated, we can start finding the solutions if we did not see them instantly. Then we have to start looking at the problem from a new perspective.

What if?

The first step is to think beyond the frames that the meeting sets. You have to change your perspective to become creative in the problem solving. Think outside the room you are in now. Change position. See the meeting with new eyes. Ask questions like for your mind.


  • How have you managed before?
    Almost everyone has done something ever in a similar situation that helped a lot. Help yourself and remind you of past successes even though they are small.
  • In your wildest imagination, how would you do?
    Drop thoughts about economy, time and other obstacles, let the imagination flow!

What would Jesus do?

I am not a believerb but have great respect for the guidance that a faith can give. A friend of mine has a bracelet with the abbreviation WWJD: What would Jesus do? He is also not particularly religious, but it gives him guidance to find the direction in the decisions he makes in everyday life. It makes him become a better person.

One can apply the same principle in professional contexts; to take someone else's perspective to think differently.


  • What would a good colleague do?
    Everyone has had a colleague who has expelled, who had solutions to problems you have had. Ask yourself "What would Matthias do?"
  • What would an expert do? What would he, as you heard, hear a keynote at a conference say or do? What would a guru say in a movie? What would they do in the pattern company?

You will be amazed at how many ideas you finally come across.

From idea to reality

Having a lot of solving ideas for solving a problem, even if they are good ideas are not enough. The next step is to see who are actually practical ideas, sort them and create an action plan.

What can you do today? Give examples of a short and simple action.
What can be done within a week?
Write a single contract where the responsibility is distributed, and clarify the process of solving the problem.

Action plan


  • I/we want to achieve the following results (goals)
  • I/we will do the following to achieve the result (method)
  • I/we will start with (schedule)
  • I/we know that I/we have achieved my/our results when the following have happened (results)

If someone is more than you responsible for any sub-method, we'll list those responsible for this so that no one misses their responsibilities.

Comments

Popular posts from this blog

Evolution Of Programming Languages in an AI perspective

Programming languages are at the heart of possibilities in software development, evolving to meet the growing complexity of the problems we solve with computers. From the early days of machine code and punch cards to the modern era of high-level languages and AI-augmented coding, the journey of programming languages reflects humanity’s relentless pursuit of abstraction and efficiency. As artificial intelligence begins to reshape the landscape of software development, we are poised to enter an era of AI-powered programming languages—tools that will fundamentally change how programmers approach their craft. From Punch Cards to High-Level Languages The earliest programmers worked directly with machine code, encoding instructions in binary or hexadecimal formats. This labour-intensive process required an intimate understanding of the underlying hardware. Punch cards, though a technological marvel of their time, epitomized the low-level nature of early programming—tedious, error-prone, and ...

The Industrial Vs the AI Revolution

The transformation of society through technological revolutions has constantly fundamentally reshaped the labour structure. The Industrial Revolution, for instance, marked a profound shift in work for the labouring classes, moving them from farmers' fields and industries into factories. Today, the so-called AI Revolution promises to bring about a similarly seismic shift, not for manual labourers but for the office and intellectual workers who were once considered relatively insulated from mechanization. While the material and historical circumstances differ, the underlying forces remain strikingly parallel. Changing the Nature of Work During the Industrial Revolution, the mechanization of production displaced artisans and craftspeople, as machines took over tasks that had required years of training and skill. This was not merely a displacement of labour but a profound de-skilling of workers, whose tasks were broken into repetitive, machine-supervised steps. The labour force expande...

Yearly Educational Goals vs. Agile Team Learning

At this time of the year, employees often have their yearly reviews and set goals for the following year. From an agile point of view, this is an antipattern. The Agile methodology promotes continuous improvement and adaptation. This philosophy often needs to match this traditional approach of setting fixed yearly educational goals for developers. This discrepancy can be analyzed regarding how these educational strategies align with the interests of labour and management within the industry (as opposed to the orchard)  and how they contribute to or alleviate the alienation and class dynamics inherent in the tech workforce. Yearly educational goals in software development typically involve predefined objectives that developers are expected to achieve within a set timeframe. While this approach provides clear targets and a sense of structure, it can be rigid and limiting in a field known for rapid technological changes and evolving project needs. Such goals may become quickly outdate...