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

Balancing Present Needs and Future Growth

In software development, traditional project planning often emphasizes immediate needs and short-term goals. However, Bentoism, which stands for "Beyond Near-Term Orientation," provides a multidimensional framework that can improve software project planning. It advocates for a balance between short-term achievements and long-term sustainability, considering both individual and collective impacts. Technical debt and architectural debt are inevitable challenges that teams must navigate. If managed properly, these debts can help long-term sustainability and growth. Bentoism, with its forward-looking and holistic perspective, offers a nuanced framework for handling these challenges while promoting continuous improvement.  Understanding Bentoism  Bentoism, inspired by the structure of a bento box that contains a variety of foods in separate compartments, encourages a broader perspective in decision-making. It promotes consideration of 'Now Me' (current self-interests), ...

Digital Dialectics: A Marxist Exploration of Technology and Class in the Software Industry

In this blog series, we discussed various aspects of programming and technology from a Marxist perspective. Here's a summary: Marxist Analysis of Programming and Technology: We explored several critical aspects of Marxist theory applied to programming and technology, including the means of production in software development, class struggle and labour relations, the commodification of software, alienation in the tech industry, and the digital divide and technological inequality. Dialectical Materialism and Base and Superstructure: We delved into applying Marx's dialectical materialism to technology development, analyzing how technological advancements lead to societal changes. We also discussed the base and superstructure model in the context of the digital age, focusing on the technical infrastructure and the evolving social and cultural norms. Class Struggle in the Software Industry: We examined the dynamics between different groups in the tech industry, including tech compa...

Software Projects as an Orchard

This blog is named The Sourcerers Orchard. The title is intended as a pun about source code and the orchard as an analogy between software development and handling an orchard. Creating a new orchard is an endeavour that blends the art of gardening with science. The same could be true for software development. We often talk about software as an industry, and this mindset harms our work. We are not an industry; we do not repetitively produce the same unit at an assembly line. We grow new things in a partly unpredictable world. Systems like SAFe are born in industrial thinking, like modern mercantilism, focused on numbers, not growth. We need a new way of thinking, to make high quality software instead of failing production lines. Planning Your Orchard Embarking on creating a new software project is akin to cultivating a thriving orchard from the ground up. It’s a journey that requires patience, dedication, and a strategic approach to nurturing growth and overcoming challenges. Let’s expl...