Thomann DNA

Even if you might not yet be working with us, that's what you can observe at Thomann:

1. It's a passionate industry. Many of us are musicians or have a hobby related to music. Music is the language of peace and community. That's why we love it.
2. Strolling around our campus in Treppendorf, you'll meet a lot of customers. It's their little D*sney Land, and we're doing everything to make their visit unforgettable.
3. You don't have to be musically to work with us. But we can't guarantee you'll never buy your first instrument anyway.
4. If it's good for our customers, it's good for us. We wouldn't be where we are right now, if it was for shareholders.

If you want some more insights on how we got there, we recommend this article on our Thomann blog about Hans Thomann's 60th birthday.

If you're looking for a more value-driven approach, check out our Thomann company values here.

You might already have recognized who created this handbook. If not, you can find our imprint here and stuff related to privacy here.

Mission / Vision

Mission statement Thomann

To inspire and enable people to speak music, everywhere.

Purpose / Vision thomann.io

We build the world's best shopping ecosystem for all people interested in creating music, audio, and events.

This part of our website helps you to understand some more details.

Strategy & Company Backlog

Thomann uses a company backlog to align strategic projects between departments and to keep track of what's going on at a high flight level transparently. You can find the backlog linked in our thomann.io change blog. In the strategy & performance section of the blog, you can also find an article describing our current strategy. It's not public, so you should definitely apply for a job with us!

How we work

remote, distributed, together

Our main communication tool is Slack. Use Slack status to communicate your availability. The easiest way is on-/offline. We provide a few other status messages, e.g. when you’re in a meeting, in a work tunnel, on break, sick or on vacation. Make sure to set them accordingly.

Iterations & flow

Most teams plan and work in iterations of 2 weeks or in a constant flow. They release as often as possible. “Done” means our customers use it.

Sync

Every team has some form of a daily or weekly update meeting. All of thomann.io gathers once a quarter for the Assembly. This is our all-hands update format.

Reviews

Our product teams show their progress and achievements each iteration to product management. They invite the whole team when useful. More infos on our reviews can be found here.

Reflection

Each team is obligated to reflect regularly. Retrospectives and project recaps are our means of choice. If your team does not have a coach of its own, please get in touch with the agile unit for support.

One department of many

Whenever it is necessary to succeed in your project, do not hesitate to connect with other Thomann departments. Expert knowledge can be found were the experts are. Connecting to others also helps you to build your network within the company.

Code of conduct

To figure out what to do when things get tough, we created a code of conduct. Look at it as a little law book. It’s great if you never need it. But it’s cool to have it to settle arguments. It contains three sections.

The baseline to fulfill our mission is

• to create empowered product teams
• to create innovative products and solutions
• to continuously deliver value for our organization

We are one team and are passionate about thomann.de and our app. We put our shared goals first and are proud of our work from day one.

How we communicate

• Honest & direct: We communicate honestly, openly, benevolent and transparent. We always tackle problems and challenges by being respectful, technical and positive. The direct approach is the best approach.
• Sharing knowledge: If something's for the world to come, document it! Information shall be available for everyone.
• Give feedback: We share positive feedback with the largest group possible: Unit → Team → 1:1. We share negative feedback with the smallest group possible: 1:1 → Team → Unit. Every team member is allowed to give feedback in any direction (360°). We reflect regularly and continuously on all levels.
• No elephants or beating around bushes: This should not exist. If it does, however, we approach somebody who is able to support us handling and solving the situation.

Our way of work

• Customers first: We focus our work on our customers, therefore it's customer first in each department.
• One remote, all remote: A good meeting provides equal chances for every participant. If one team member joins remotely, all other participants shall join the meeting remotely and separately.
• Let's be pioneers: We take a step further than other e-commerce companies. Our ideas, features, team and ways of work shall be an inspiration for others and set the bar high.
• Minimal change: The smallest change shall be validated with real customers as fast as possible. A great foundation is better than a house no one wants to live in.
• Continuous improvement: We constantly learn to improve quality and processes, while concentrating on our strengths as well as striving for autonomy and empowerment.
• Have and feedback ideas: Each idea helps us improve. Therefore, they shall always be put in our Feedback Hub. Consult others and remember: the inside of the box might only be one perspective.
• Take ownership: We work driven by solutions, quality, success, and data. The teams own their product (or product parts) and code. They are responsible and accountable. Each role contributes with their own skills.
• Consult others: If we are unsure about making a decision, we seek help from experienced team members. This also helps us to feedback ideas and prepare them for our Feedback Hub. All team members are consultants for each other.
• Work in teams: Our way of work is inspired by established processes. However, we own and adjust them when needed. We bank on long-term, cross-functional teams working location- and platform-independent.

No Gos

• Office grapevine: We avoid hidden priorities, agendas, and the distribution of wet ink. What counts is communicated transparently and explicitly.
• Getting stuck with your mindset: We avoid being biased. There is no "we've always done it this way" or "this will never work" without valid data and experience.
• Hidden feelings: We don't hide our feelings. Bad feelings tend to bottle up. We don't want you to listen to My Chemical Romance.
• Complexity & waste: We avoid unnecessary complexity on all levels. The most obvious solution tends to be the most reliable. Therefore, we try to reduce waste continuously.
• Finger pointing: It's not your fault. Mistakes happen all the time. We support each other to have them only happen once and to improve ourselves. Nothing's just someone else's problem.
• Talking about "the others:" We are one large team - thomann.io. Even though we all have different roles, there are no "others" in our team. We share one common goal and every team member contributes with their skills.
• Head monopolies: We don't like them. Each head can fit some more of the other team members' knowledge.

Our position on politics

At thomann.io, we are focused on building an economically successful and sustainable company. While we value diversity and inclusion, we aim to remain politically neutral in all aspects of our business operations. Our employees hold a diverse range of political views and opinions which we respect. However, we do not engage in political protests, campaigns or partisan discussions in the workplace. We do not discriminate against or take action against employees and potential candidates based on their nationality, personal political views or affiliations. Our goal is to foster an open environment where all employees feel comfortable being themselves, without having to walk on eggshells or self-censor. We have seen many companies suffer from taking partisan political stances, and believe it is in our best interest to remain neutral and focused on our business goals. At thomann.io, we aim to judge our employees solely on their merits, talents and contributions to our company's mission.

Reviews

#prod-review is used by all teams that will present something new to everybody (colleagues, stakeholders, customers). Reviews take place every week. You are invited by default and each session is open to join for everybody. Each product team has a 30 to 60 minute slot to show the last weeks’ progress and share thoughts with stakeholders and colleagues from other teams. It is the responsibility of all product teams to prepare the review, invite stakeholders and update all non-attending team members on what’s been shared.

In order to help you with creating reviews that are informative and have the right scope here are some guidelines (not rules) for creating a good team review:

1. Give a brief intro to topics: why is your team working on this topic? What’s the value of it?
2. Tie lines of code to value, keep code low and focus on the value. This doesn't mean don't show code, it just means keep it on a certain level of detail.
3. Involve the audience when possible. If you can, pose questions to the audience or encourage them to give feedback.
4. Take some time in the teams for preparation. Your team is 100% enabled to take time for preparation, 5 minutes before team review may be too short.

Reviews are also recorded and shared afterwards through the respective Slack channel.

First steps & what awaits you

Welcome to the thomann.io team. We're thrilled that you're on board. Arrive calmly, sit back and let us surprise you.

In the first few weeks, you should find your way around and get to know people. To help you do that, you have a wonderful support system by your side: your buddy, lead, team and of course P&C and the agile coaches. In other words, a bunch of nice people who will introduce you to the Thomann.io cosmos.

To help you celebrate your first successes quickly, you will be given your first tasks in the first few weeks. These should also help you to get in touch with your new team. In addition to the professional exchange, we would also like to get to know you personally. You can look forward to many coffee calls.

To help you figure out what we expect, you will get everything clarified in the first week in an extra expectations meeting with your lead. But then it's up to you: we love feedback, so keep it coming! What can we do better? A fresh pair of eyes is always good. Don't hold back and exchange ideas with your buddy and the P&C unit. Within your first quarter the P&C unit will come to you to find out how you are doing and how the recruiting/onboarding process went.

After 3 months, you should know the most important contacts at Thomann Cosmos. Use the regular exchange with your colleagues for knowledge exchange, feedback or just to chat about the weather.

Onboarding buddies

Your buddy will help you find your way around the thomann.io.

They will coordinate your first meetings and introduce you to the people you’ll work close with everyday.

You and your buddy will hold regular feedback sessions in the first 6 months and beyond to make sure you can arrive in your new role properly.

Your buddy is the #1 go-to person for any questions. By the way, there are no stupid questions. But you already know this.

In addition, people & culture will ask you for feedback and any concerns during your first 6 months.

Expectations

Once you start your lead will share expectations for the first months with you. In some occasions, they might be shared by your onboarding buddy.

During your probation period and onboarding As a rule of thumb, you will receive much more feedback during your probationary period than afterwards.

Feedback meeting: Your feedback about recruiting and onboarding

At the 3-month point, we want to receive feedback from you. How was the recruiting process? What went well, what could be improved? H ow are things with your Onboarding Buddy? Did we miss anything? Your feedback is important for our people and culture unit. Feel free to also voice any criticism.

Feedback meeting: The 3-month-talk

It's half-time! After 3 months, you’ve already made it through half of your probationary period. This talk is here to check how happy you are with your role and if your tasks and responsibilities are meeting your expectations. At the same time, your lead will reflect on the work you’ve already done and will give you some feedback on it.

Feedback meeting: The 5-month-talk

Nice! You’ve almost completed your probationary period. This talk again serves as a check-in on you and your satisfaction within your role, team and the company. Same as before: your lead will give you an overview of your achievements and on parts that could be improved. Together, you’ll define the goals for the future and the path you will take in the next months.

Important: Make sure, you are transparent about where you need help or if there's some expectation that might not fit your role. After your probationary period, you will then proceed with our basic career development and feedback cycles.

Be the best buddy

As a buddy for a newbie, you are the first point of contact. Regardless of whether it's technical or team-related: you support the newbie with all of his/her questions and make sure she/he is doing well. The most important thing is to build a relationship of trust between the newbie and you. The newbie should feel comfortable and that is the number one priority for you as a buddy. To prepare you for your tasks, you will receive a buddy workshop from the P&C team.

Your tasks start before the newbie's first day (see onboarding checklist). You are responsible for making sure that the onboarding runs smoothly and that the newbie has all the information before the first day (e.g. start, agenda first day).

On the first day, you give a first introduction to the most important tools (e.g. Slack, Google Workplace, Kenjo), the team structure ("who does what") and the most important processes (e.g. meetings).

In the first weeks, make sure that the newbie is well-connected in the company and knows the most important people (lead community, coaches, P&C, etc.). Together with the lead, clarify the expectations of the newbie so that his/her role is clear to all parties. If you are unsure about this, feel free to approach the onboarding community or your lead.

It is important that you keep in touch with your newbie throughout the probationary period. Jour fixes or bi-weekly meetings can help to identify and clarify questions or uncertainties early on. The most important questions are:

• "How are you?"
• "How can we support you?”

If you have any questions, please contact the onboarding community #io-onboarding-buddy-general-information.

Feedback meetings

Regularly

During the probationary period, it would be great to give feedback to your newbie throughout. Important points are:

• What is already working well?
• Where do you see opportunities for development? Be sure to get feedback from others (e.g. coaches, colleagues, etc.).

During probationary period

Make sure you organize all necessary meetings for your newbie stated here.

Afterwards

You can certainly stay in close contact with your newbie beyond the probationary period.

We show ourselves to other team members

We are a large department already. Working fully remote doesn't make it any easier to find your way around as a newbie or when looking for people you haven't worked with in a while.

Profile pictures & clear names

Set a profile picture in at least Slack and Kenjo in your first week of work. Google Workplace is a bonus everyone will thank you for when configuring access rights. Make sure the picture shows your face for others to recognize.

For Slack and Kenjo use your full name as profile name and display name. In your Slack profile, add your role & team in the title section.

This helps everyone, to find their way around our organization.

Nicknames

Some team members are often referred to by their nicknames. If you are one of these lucky people, please put your nickname in quotation marks between your first- and lastname, i.e. Firstname "Nickname" Lastname. This is the easiest way to search for you. You only need to apply your nickname in Slack.

Default: camera on

Video killed the radio star at some point. Our default in all calls is to have your camera turned on. There might be exceptions with bad internet connection, e.g. when traveling, or personal well-being.

Psychological safety

Important: if you feel, you're in a situation where psychological safety is not granted, approach a person of trust to support you. These can be, but are not limited to, persons from people and culture, your manager, a peer, or the agile coaches.

How can you contribute to an environment of psychological safety?

• Embrace a culture of respectful debate.
• Encourage personal storytelling.
• Ask questions.
• Allow for experimentation and failure.
• Model openness to feedback.
• Set clear goals and key performance indicators.
• Offer development opportunities.
• Build a speak-up culture.
• Highlight competencies.
• Dismantle perceptions of hierarchy.

We're all in this world together. Therefore, we can be certain that other people share similar challenges as ourselves. From time to time, it's a good idea to visualize the following:

• This person has beliefs, perspectives, and opinions, just like me.
• This person has hopes, anxieties, and vulnerabilities, just like me.
• This person has friends, family, and perhaps children who love them, just like me.
• This person wants to feel respected, appreciated, and competent, just like me.
• This person wishes for peace, joy, and happiness, just like me.

Huge kudos towards Gitlab for providing great content on this topic in their handbook.

Mental health

Mental health at work refers to the impact of work on a person’s mental well-being. It encompasses the psychological, emotional, and social aspects of work, including job tasks, work-life balance, relationships with colleagues and superiors, as well as the organisational culture. Thomann.io is aware of its responsibility to create a supportive work environment that promotes mental well-being, and offers resources for those who want support.

Please contact the people and culture unit at any time with questions. In urgent emergency cases and if you think we are not the right contact in your case, you will find competent help on 116117.de.

Management

We believe in the value of managers to drive results for the company, support teams and enable growth for individuals.

A manager’s job therefore can be divided into two areas.

• Making the company successful
• Taking care of their people

Making the company successful means delivering on company goals.

A manager has to deliver results with their team. They have to set the right context for their team. The other nature of your role is being a consultant for the company; when you are an engineering manager, you get questions about engineering and need to be able to have or get the answers.

Taking care of their people is the other part of the role.

You can have great goals, but what are goals without a team to help work towards them? As a manager, you have to build and retain a performing team by growing individuals, fostering collaboration, and recruiting talent. Taking care also means affording the team enough freedom to do their best work.

These areas are not only connected, but they depend on each other. Making the company successful is the WHY and taking care of their people is the HOW.

It doesn’t help if the company is successful, but its employees are frustrated. But there is also no value in having a happy team when the company is underperforming.

One manager should not have more than 8 direct reports over a longer period of time. This limit makes it possible to build genuine and trusting relationships.

Management career path

Here's an overview of our management career path. To dive in deeper, please refer to the career development handbook.

Manager stage 1

The shift from individual contributor to team lead comes with new responsibilities. Managing daily work, identifying improvement areas, and addressing skill gaps become central. Involvement in technical decisions and a solid grasp of agile principles help navigate team dynamics. A focus on team performance, using metrics like flow, ensures steady progress. Strong communication skills enable effective collaboration. Over time, the role evolves into proactively improving workflows, removing obstacles, and fostering a motivating environment through structured feedback and support.

Manager stage 2

With growing experience comes a shift to more strategic responsibilities. Decisions are driven proactively, methods and frameworks refined, and team improvements aligned with the bigger picture. Providing feedback, collaborating with the agile coach, and addressing skill gaps strengthen team maturity. A belief in growth through feedback shapes leadership, along with an understanding of key drivers like autonomy, results, and purpose. Over time, the focus expands to coaching, creating space for reflection, and ensuring the team’s work aligns with the company’s mission. Communication and leadership styles adapt to each individual, while influence extends to organization-wide decisions.

Senior manager

Leadership expands to multiple teams, focusing on driving the organization forward and translating company goals into action. Developing teams through strategic initiatives ensures long-term growth while supporting key initiatives without becoming a bottleneck. Decision-making extends across the organization, with a focus on balancing strategy and execution. Thoughtful use of team strengths and weaknesses fosters development and sustained progress.

Leadership learning path

To ensure our managers are well-prepared for their roles, we offer an internal leadership training program. This program consists of five modules designed to build essential leadership knowledge. The training is primarily aimed at new leads, but all managers are welcome to participate.

• Module 1 covers the foundations of classic management 3.0 and is currently conducted externally.
• Module 2 focuses on employee communication and team leadership, including communication essentials, practical exercises for handling difficult situations, and guidance on structuring 1:1 meetings.
• Module 3 explores the entire employee lifecycle, providing a solid understanding of attraction, recruiting, onboarding, retention, growth, and offboarding, along with relevant resources.
• Module 4 delves into labor law and HR essentials, covering key legal principles while specifically addressing the manager’s responsibilities.
• Module 5 focuses on self-management, resilience, team performance, and maturity. It provides resources, tools, and methods to help managers build high-performing teams.

Meetings

Own the meeting you schedule. Make sure you provide an agenda and information about what the outcome is supposed to be. Facilitate the meeting to keep it efficient and effective. If you need help, ask one of our coaches for support. If agenda and outcome are still unclear, postpone to work on clarifying things first.

Give your meetings a title that makes sense. We’re growing, not everybody is into all meta-humor threads anymore. Like writing code, use meaningful meeting titles and add a short description. This helps people to know what it’s about and to opt out if they can’t add value.

Give your meetings a timebox that calls for freedom. 8 working hours should not be 8 meeting hours. Make sure you give yourself enough time to process meetings and work on your action items. It’s okay to say no to a meeting and it’s okay to opt out, if you’re not sure what to contribute. Schedule meetings for everybody to be able to use the bathroom or make a coffee in between, e.g. rather setup 45 minute meetings than 60 minute meetings.

Pay some respect, be on time. Be on time to your recurring team meetings, e.g. every team member should know when their daily is. All recurring team meetings happen according to the shared thomann.io calendar or team calendars. If they don't, you'll be notified.

Cancel meetings on time. Cancel your appointments when you take vacation. If possible, also cancel them while sick. Cancel them, while you travel and might be stuck with WIFIonICE…

Don't multi-task. People make time to join an appointment with you so please value that and treat it with due respect. Don't type away in Slack chats while being on a call, don't pick up the phone unless it's an emergency and speak up if you get the feeling you have nothing to contribute instead of zoning out.

Consider making your calendars and meetings publicly accessible to everyone in the organization. Public calendars can improve collaboration, transparency, and accountability. By sharing your schedule, you help others coordinate more effectively, avoid conflicts, and identify opportunities for teamwork. This initiative is entirely voluntary, and we respect individual preferences regarding privacy. For those interested, a detailed guide on how to make your calendar public is available in Confluence.

Your career at thomann.io

In this section, you'll learn which career paths you can choose from and how our feedback culture works.

Basics: Seniority and soft skills

Regardless your career path, there are a couple of general expectations tied to your personal seniority. We're not into the big title game but this overview helps you to understand what behavior we expect when placing people in their according roles.

Our career development is structured in basic seniority levels. Depending on the unit you'll be working in, there might be different numbers of stages, e.g. 2 as a junior, 2-3 as a senior. Depending on the size of your unit, there might also be different seniority levels, e.g. the engineering unit has a staff level, whereas others do not (yet).

Trainee/working student/intern

At this stage, you'll be making your first steps within your subject area. You'll acquire some basic knowledge and start to know what you're talking about.

We expect you to be curious and to ask a lot of questions proactively.

Junior

You have basic knowledge in your subject area. You take over projects on your own. You still ask more questions than you're able to answer.

Junior Stage 1: Basic communication skills, teamwork, learning agility, adaptability, time management, and respect for diversity.

Junior Stage 2: Advanced communication skills, basic conflict resolution, decision-making, goal setting, problem-solving skills, and improved learning agility.

Mid level

You have extended knowledge in your subject area. You take over projects on your own. You can answer more questions than you have to ask.

Mid-level Stage 1: Advanced conflict resolution, effective feedback skills, empathetic listening, creative thinking, and self-motivation.

Mid-level Stage 2: Leadership skills, project management, negotiation, strategic thinking, and emotional intelligence.

Mid-level Stage 3: Delegation, coaching, advanced leadership skills, advanced project management, and change management.

Senior

You have expert knowledge in your subject area. You function as a mentor for new team members in your subject area through onboarding, sparring or teaching. You are able to prioritize tasks in accordance with our customers and product vision and help others to do so as well.

Senior Stage 1: Advanced strategic thinking, crisis management, mentoring, resilience, and influencing skills.

Senior Stage 2: Advanced influencing skills, diplomacy, organizational skills, stakeholder management, and vision setting.

Senior Stage 3: Advanced organizational skills, decision-making in ambiguity, advanced vision setting, cultivating a culture of respect and integrity, and servant leadership.

Staff

You have expert knowledge in your subject area and a great understanding of company-wide business initiatives. You connect the dots across units, teams, and communities.

Staff Stage 1: Executive communication, succession planning, advanced diplomacy, advanced stakeholder management, and advanced servant leadership.

Staff Stage 2: Visionary leadership, strategic partnerships, shaping company culture, thought leadership, and advanced succession planning.

Career paths

Each unit offers two different career paths and a lot of different roles.

Expert

You like to dive deep into the rabbit hole of your expertise area? Awesome! You can advance your skill set in your subject area and become an experienced senior, some units might also offer staff level positions.

Management

You like to lead and enable people? You love to see them become experts? Great! You can grow into a management role and help your team to become empowered. One thing to keep in mind here: taking over a management role might take some time. We're not growing in lightspeed as a company. Therefore, it can take some time for a new management position to be available.

Important note: No matter on which path you decide, there will be no monetary differences. The pay ranges will be similar based on your seniority and your experience within thomann.io.

Changing roles: If you’re unhappy in your current role, just talk to your lead. If you see a role on our jobs page that might be a fit for you, just apply. It’s as simple as that.

Career development

To make it as simple and transparent as possible for each team member to decide for next steps in their career, we created a career development handbook. It's accessible for all team members and includes all templates and process descriptions for career development and salary. You can find it as Career Development & Salary Process in your shared drives.

Important to know: each team member is responsible for their own career. Your manager is not supposed to run after you to develop your career. While the process is highly collaborative, initiation best comes from yourself.

Career development conversation

Once a year, a team member and their lead person will conduct a career development conversation. From a legal perspective, this reflects the yearly performance review, appraisal interview, or whatever you want to call it. It is split into a few different phases, consisting of a self-assessment, peer-feedback talks, the actual conversation with your lead, and if applicable a salary adjustment.

Your lead will share all necessary documents with you during the process and guide you through all your questions. Especially when you're new to the process, make sure to use a copy of the checklist document. If you have questions about your career development during the year, feel free to reach out to your lead or a team member from people and culture.

Templates

All templates for the official interviews can be found in the career development shared drive.

360° Feedback

A great feedback culture lives from having the option to give feedback any time, any place. And even though this is great, it is important to provide regular, obligatory formats to collect and give feedback. Our guidelines on feedback culture can be found in our code of conduct.

Ad-hoc people and culture sessions

The people and culture unit offers an open ear to anybody in the team. If there’s something you’d like to talk about, just approach a person from the people & culture unit. This appointment is not obligatory but highly recommended. You can talk about your current situation within thomann.io. You can use it to talk about things you may not want to share with your lead person yet and get support preparing for it. Or just to get another perspective on how to achieve your goals or organize a training.

Weekly 1:1s

1:1s shall be used for continuous feedback, e.g. recapping your peer feedback sessions or where to go next on your journey through thomann.io. You can also use it to address obstacles in your daily business and to get advice on how to cope with challenges. Another important aspect is to feedback your lead person and address issues that are important to you.

Peer feedback

Once a year, you have to organize at least 2 peer feedback sessions.

1. a talk with a team member you work together a lot (approx. 80% of your time). Let them answer the questions below.
2. a talk with a team member you spend less time with (approx. 20% of your time). Let them answer the questions below.

Questions:

1. What did I contribute to Thomann.io in the last 6-12 months?
2. What do you appreciate working with me?
3. From your perspective: In which areas should I grow to develop myself?

You can do your sessions reciprocal, interviewing each other. But make sure the second person is not biased from the first interview round. You do not need to talk contents with your manager. But let them know once you're done since peer feedback is the starting point for your yearly career development.

Important note for the 20%-team-members: short feedback is fine. Don't worry to not have as much content as an 80%-team-member. Not observing negativity can be a positive feedback as well.

Probationary period

You will receive feedback within your probationary period. Refer to the onboarding section for more information.

Recommended feedback formats

The BIO method for preparing feedback

The BIO method is a structured approach to giving effective feedback, focusing on clarity and constructive improvement. Preparing a feedback session with this method helps to ensure feedback is specific, impactful, and actionable.

• B - Behaviour: Clearly describe the specific behaviour you observed
• I - Impact: Explain the impact of that behaviour on you, the team, or stakeholders
• O - Options: Focus on the future by suggesting options for improvement. Emphasize that these are suggestions, and the decision on how to move forward remains with the individual receiving the feedback

Feedforward canvas for personal development

The feedforward canvas, in collaboration with a "feedforward buddy", helps you actively utilize feedback for your learning and development goals. It is designed to bring the act of asking for feedback into a structured format that doesn’t stop at getting feedback. It emphasizes working on a goal through experimentation and continuous improvement with the help of an ally. The template can be found in our Miro template library.

How to use:

1. Pick your goal: This can be something you recently discovered yourself, got aware of in a feedback conversation, or even one of your goals from the career development conversation
2. Find a feedforward buddy: Choose someone you trust, who can provide valuable feedback and advice. Anybody can function as a feedforward buddy. It doesn’t have to be your manager
3. Collaborative process: Work through the canvas together, focusing on implementing change through small experiments
4. Revisit: Review the experiments' outcomes

Key Principles of the Feed Forward Canvas:

• Focus on future actions and experiments
• Emphasize learning and growth through iterative feedback
• Utilize a "feedforward buddy" for support and perspective

1on1 meetings

As stated in the career development handbook, 1on1s between individual contributors and their managers are an essential part of our feedback culture and the go-to-place to talk about any situation that might affect both participants' work relation.

We recommend to have weekly 1on1s. These should be documented and follow a predictable and easy-to-prepare structure. This exemplary template can, for example, be used in a Google doc or in Notion for each 1on1. Thus, the 1on1 can be prepared beforehand and the appointment can focus on conversation.

1on1 template

Date <xx.xx.xxxx>

Topics/what's on your mind

• …

What was your highlight/lowlight in the last 7 days?

• high:
• low:

Is there anything you need help or context with?

• …

Is there any feedback that needs to be communicated?

• Direct:
• Manager:

Is there anything you want?

• …

Are you happy?

• Direct:
• Manager:

What was the most useful for you in our session today?

• …

Misc topics (things, the manager wants to talk about)

• …

Other 1on1s

Usually, team members also have 1on1s with peers, stakeholders, people from other divisions or units, etc. In these cases a different format might make sense, e.g. using a Slack channel to share topics or loose ideas.

Thomann.io as an organization

thomann.io GmbH itself integrates into Thomann Universe just as any other department would. thomann.io functions as Thomann’s tech and data department for customer-centric IT. Thomann also employs employee-centric IT teams (e.g. service center, internal IT) in our Treppendorf headquarters.

Besides us, there are many other departments, e.g. marketing, logistics, purchase management, sales, customer care, hr, audio professional, etc.

Leadership

• Chief digital officer: Dr. Christian Maaß
• Managing director thomann.io & director product: Jöran Eitel
• Director technology: Daniel Hauck
• Director data: Arman Savuk
• Director organization: Ralph Cibis
• Director finance: Meike Langer

Leadership shall be seen and interpreted as a service we provide for all our employees.

Responsibility and accountability

Responsibility

Responsibility refers to the obligation or expectation to perform a task or role within a specific context. It is the duty to complete an assigned task or fulfill a particular function. Responsibility can be shared among multiple individuals, and it can change as the situation evolves.

Accountability

Accountability, on the other hand, is the state of being answerable for the outcomes or results of a task or role. It implies that an individual, team, or organization is held liable for their actions and decisions. Accountability cannot be delegated or shared; it is always assigned to a specific person or entity, who must own the consequences of their actions, whether positive or negative.

Organizational structure

The organizational structure takes place within units and helps us to clearly define responsibilities and accountabilities.

Though, not every level is filled in each unit, we decided to define a structure similar to many companies in our field and not reinvent the wheel on this one.

Overview

Roles

A role‘s responsibilities are the accountabilities of the next level. For some roles in our units there might be additional responsibilities and accountabilities. This overview, however, provides information on what is applicable for these levels company-wide.

Individual contributor

Responsible for

• Executing assigned tasks effectively and efficiently
• Collaborating with their team members and other teams within the organization
• Reporting their progress and providing feedback on ongoing projects
• Continuously improving their skills and staying updated with industry trends
• Adhering to company policies and guidelines

Manager

Responsible for

• Guiding teams on functional choices
• Overseeing the value stream
• Facilitating personal growth of their team members
• Collaborating with other teams, such as product management and quality assurance
• Taking care of disciplinary matters, like salary and vacation

Senior manager

n/a

Lead

Responsible for

• Establishing and monitoring performance metrics and delivery goals
• Addressing challenges and streamlining processes
• Ensuring coordination with other teams and units within the organization
• Recruiting and managing team members
• Facilitating regular communication across team members, directors, and stakeholders

Director

Responsible for

• Sharing the organizational mission and answer questions in regard to it
• Ensuring the alignment of division objectives with the organization's overall strategy
• Managing budgets, resources, and unit leads
• Collaborating with other divisions and business units

Chief digital officer

Responsible for

• Developing and implementing a cohesive digital strategy
• Overseeing technology investments and innovation initiatives
• Ensuring cross-functional collaboration to promote digitization
• Identifying areas for digitization and automation
• Managing digital partnerships and alliances

Current divisions and units

• Division Product
  • Units: Product, UI/UX/UR
• Division Technology
  • Units: Shop Engineering, Quality Engineering, Architecture, Operations, Tools Engineering
• Division Data
  • Units: Data Analytics-/Science, Digital Analytics & Measurement, Data Engineering, Business Intelligence
• Division Organization
  • Units: People & Culture, Agile Coaching, Organizational Development
• Division Finance
  • Units: Finance, Business Administration, Office

Divisions

Divisions are areas covering a broader, more general topic. Each division is led by a director and consists of multiple units.

Current divisions are product, technology, data, organization, finance.

Units

Your unit is your home base and lives within a division. A unit has a lead that takes care of disciplinary topics and the technical direction of the unit. Units from similar areas report to a director to provide a scalable structure.

Scale & leads

Some units are already large enough to have their own lead persons. There might be different factors to be taken into account when creating a new lead role for a unit:

• the amount of team members working in a unit
• the complexity of the topic a unit covers
• how the unit has grown over the years Small units might still be led by the director of the unit's division.

Operational structure

Overview

Units, teams and communities

Our roles at thomann.io are clustered in different units. Each unit provides different roles. They all assemble in product teams, service teams, or communities. Each team has free choice about their means of work and process frameworks, as long as they contribute value for our customers in regular, short iterations.

Teams

Teams make for our operational heart at thomann.io. No structure and hierarchy should block a team from succeeding.

Stream-aligned teams

• customer-centric to the users of our web shop and app
• data- & metrics-driven
• focus on domains, e.g. app, purchase experience, storefront, discovery

Stream-aligned teams combine roles from engineering, product, uiux, and agile to own parts of our web shop and app. They work together with service teams to succeed in their projects.

Platform teams

• engineers and other internal roles as customers
• focus on foundations, e.g. development experience, frontend experience, infrastructure, testing, data engineering

Platform teams usually have their competency in one unit. They build the foundation for our stream-aligned teams to succeed. They might also support other departments from Thomann.

Enabling teams

• focus on consulting other teams and supporting them in achieving their goals
• e.g. architects, operational support, data support

Switching teams

Should a team member not feel comfortable (like really uncomfortable) with their team, there's an option to switch teams. The highest priority here is to look for direct communication. There are some requirements for finding/forming a new team:

1. Functioning teams must endure
2. Teams must be able to develop features for their focus topic
3. Teams should consist of people from multiple locations
4. A new team constellation shall improve our product development

Making teams visible

Make sure your team has a blog post on thomann.io. This will help you introduce the team to your applicants. Important: You own the post. If your team changes, you must change the post as well.

Sync rounds

To ensure collaboration within our teams, the right people on the right level should regularly talk to each other. Therefore, team sync rounds are in place. Their primary focus is on ongoing product development and potential blockers. All other team-related topics are secondary but can be discussed in this format as well.

The main artifacts of a sync round are the company backlog and the respective team backlogs deriving from it.

Escalating blockers (and other important topics): if a sync round does not know who the right person is to escalate an issue to, it's the coaches obligation to escalate it to the next higher round.

Team sync rounds (TSR)

• Consists of PO/PM, coach, and engineering manager
• Syncs about topics on epic level, team workflow, and drives team-internal collaboration
• Syncs on feasibility regarding the team's quarterly plan, collaborates in planning a team's next quarter
• Connects with and involves all necessary people (e.g. data, stakeholders, architects) to succeed in making their epics reality

Shop sync round

• Consists of the leads for product, design, coaching, shop engineering, and data analytics & measurement
• Has an eye on cross-team dependencies and drives cross-team collaboration to resolve them, i.e. bringing the right people together and updating the right people
• Tackles blockers and issues arsing within an initiative, escalates those that cannot be resolved directly to the company sync round

Company sync round

• Consists of the directors for product, data, tech, and organization
• Is responsible for the all-over development process, the team members involved, and the outcome released
• Is the escalation point for all blockers and issues that cannot be resolved by the other sync rounds

Structure within teams

Most of our operational teams thrive on a collaborative structure designed to address key aspects of product development and delivery. This often involves engineering managers, agile coaches, and product owners or project managers working closely with essential individual contributors like UX/UI designers, quality engineers, and software engineers to achieve team success.

Product owners or project managers (effectiveness)

Their main question is: are we doing the right thing?

• Align with business goals
• Track business metrics, e.g. no. of checkouts, cvr, aov
• Prioritize customer and stakeholder requirements

Agile coaches (efficiency)

Their main question is: are we doing things right?

• Coach teams to maturity and performance (mission statement agile community)
• Track agile metrics, e.g cycle time, waiting times, bottle necks, wip
• Support team roles & stakeholders to work in an agile context

Engineering managers (skills & tech strategy)

Their main question is: do we have everything in our team to do it?

• Development of team members personally
• Keep tracking of required skills
• Ensure technical excellence

Individual contributors

Each team benefits from a combination of diverse individual contributors crucial for success in their domain and projects. For product teams, this often includes engineers, UI/UX designers, and quality engineers. Service-oriented (platform/enabling) teams typically consist of a more homogenous group of roles, such as operations with admins and DevOps. Similarly, our data division includes individual contributors with specialized roles focused on data analysis, engineering, and science.

UX/UI designers (user experience & accessibility)

Their main question is: are we building it for the user?

• Ensure designs meet accessibility standards and are inclusive.
• Create and refine user flows and layouts based on user needs.
• Review implementations for adherence to design specifications and provide guidance.

Quality engineers (testing & release reliability)

Their main question is: are we releasing a high-quality, reliable product?

• Drive quality engineering best practices and advocate quality across teams.
• Develop and maintain robust test frameworks, introducing cutting-edge tools and technologies to enhance testing efficiency and effectiveness.
• Provide guidance to teams on necessary tests, ensuring comprehensive test coverage at all levels (unit, integration, end-to-end).
• Ensure thorough testing of products before merging code, guaranteeing a seamless and exceptional user experience.
• Collaborate closely with developers, product managers, and designers to proactively identify quality risks and ensure rapid resolution.

Software engineers (implementation & technical excellence)

Their main question is: are we turning requirements into software that is functional, efficient, and easy to maintain?

• Translate requirements into functional, robust and easy-to-maintain code.
• Consider and own the long-term success of our technical solutions.
• Ensure code quality through unit and integration testing.
• Participate in code reviews, providing and receiving constructive feedback.
• Maintain and adhere to organizational coding standards.
• Build software in continuous small increments and improve through early feedback.
• Deploy code changes and new features, ensuring seamless integration and adherence to the Definition of Done.

Communities

Communities are groups of team members that work on a shared goal that is not yet part of a team or reflected in the general duties of a unit. Every team member can join or create a community and colleagues outside our organisation are of course welcome to participate as well.

Endurance

Communities can exist for a long time (e.g. documentation, diversity, business administration) or just for a few days or weeks (e.g. to organize a team event, to finally fix a bugging issue).

Topics

Topics can range from specialized technical topics (e.g. checkout flow, database naming) over more general topics (e.g. security, artificial intelligence, user research) to cultural ones (e.g. organizational development).

Requirements & rules

• A community needs a clear goal and a couple of first tasks or action items that will help to achieve the community's goal
• A community is led by a single team member (community lead), whose responsibility it is to
  • define the community’s goal
  • align the community with the company’s business goals
  • lead the community towards achieving its goals
  • document and communicate the community’s progress
  • close and archive the community if necessary
• Every team member that joins a community must actively and regularly contribute
• A community should meet in fixed intervals (monthly, quarterly,...) but always in a resourceful manner, when it comes to invested time and frequency

Initiation

Once you’ve come up with an idea, take it to the next 1:1 with your manager and pitch the idea. They can help you challenge the idea, give you a better perspective on how to align the idea with our business goals, and if there might be a similar initiative going on already. See your manager as your sponsor to free some time for you and also to back it up.

With this information, you are free to decide whether to found a new community or not.

Starting and running a community

Starting

• Create a public “community-” Slack channel (private only, if it’s REALLY necessary)
• Send an @channel message in #io-team-all to inform everyone about the new community, on its goal, and maybe what skills you’re looking for in your contributors
• Schedule a community kick-off meeting

Running

• Meet as proposed in the rules above
• Hold the community members accountable in terms of contribution
• Regularly reflect on the community, its goal, and its right to exist

Documentation & communication

As a community lead, you have to make sure that either you or other contributing community members document the progress and results of a community. In the past, Confluence pages or Miro boards proved great for doing this collaboratively.

Outcomes of a community may also be part of a review, an Assembly, or a unit update, depending on which audience is relevant for the results. To include outcomes, you simply connect with the people working on these formats.

Completion

A community has come to an end due to the following reasons

• Its goals have been achieved and found their way into our day-to-day work, e.g. became part of a product team’s backlog, or a standard everyone complies with
• People are barely contributing to the community
• The community’s goal does not comply with our company mission anymore

In case it’s about time to close the community, make sure to document the final outcomes and archive its Slack channel.

When to not create a community

If you’re just looking for a place to exchange thoughts, content, or perspectives, please consider some other formats available:

• Invite for a coffee call about a topic
• Talk about your topic at our open space
• Use an existing Slack channel and start a thread, e.g. #misc-random, #misc-music, #misc-io-expats, #tech-talk
• Create a Slack channel for sporadic exchange, if something interesting pops up, e.g. #misc-typescript-addicts, #misc-cat-owners-of-io

If a topic does neither comply with our business goals nor our company culture, please refrain from proposing a community.

Benefits

X-Mas money

We pay a 13th salary together with the November salary.

Company pension scheme

We offer a company pension scheme (betriebliche Altersvorsorge) for all of our employees from Germany. You can top the employer contribution tax-free with money from your gross salary (regulations apply). From the employer side, we offer the following subsidies:

• 0-2 years with the company (after probationary period): 50€/month
• 2-5 years with the company: 75€/month
• 5+ years with the company: 100€/month

Employee discount

You receive Thomann employee discount. The discount depends on a product's margin but in general is the purchase price + VAT + what it costs to move the product through logistics.

You can use our employee price tool to calculate the price by providing the URL or the article number. A link to the tool is attached to #io-team-all.

How to order: For each order you make as an employee please use the comment field in the checkout to write down the following information “Employee at thomann.io; Account no.: {Your customer account number}“, which will then be stored within your customer data, so that you can simply take discounted orders automatically in the future.

The discount will, however, not be given in the checkout. Your identity will be checked for eligibility first and the order processed afterwards. You can still use your preferred payment method. The payment in full will be put on hold and after verification only the discounted price will be charged.

Existing & new customer accounts

• When you start with thomann.io, let people and culture know your customer account number during the onboarding process
• When you create a customer account after you've started, please forward your new customer account number to people and culture

Equipment

We try to fulfill your wishes regarding working equipment. However, we will in some cases propose hardware that fits your role. Working students will usually get equipment that we already have in stock.

Coaching

We offer our team members systemic coaching with external coaches. If you need someone to listen to you, to provide a different perspective, or to challenge your ideas and thoughts, just sign up for a session. There are two systemic coaches to choose from. The sign-up links are bookmarked to their Slack channels #misc-coaching-with-sabrina and #misc-coaching-with-gotthard.

Sport/Food etc.

In Treppendorf there's a gym and a canteen. The gym is brand new and offers everything you can think of. The canteen, our t.kitchen, offers warm meals during the day, and you get employee discount on food and drinks.

For remote positions/other offices: we have a cooperation with urban sports club and a discounted membership for employees. With urban sports club you have many possibilities to take part in sports activities in your area.

Corporate benefits

For those of you who are also interested in buying from different shops we also have a cooperation with Corporate Benefits. With Corporate Benefits you´ll receive ongoing attractive offers from famous brands, which you can redeem in online shops or also in store directly on site. You can easily sign up with you thomann.io email address at Mitarbeiterangebote.

Referral program

If you know a great candidate for one of our vacancies, we’d love to hear about them! We truly appreciate all recommendations, but please take a moment to consider whether the person is not only a good team fit but also meets the necessary formal requirements. If everything works out, and it leads to a hire, you’ll receive 1000 Euros after the newbie has passed the probationary period (6 months).

You get the bonus for all successfully placed full-time team members (working student positions are excluded).

Any questions? Then get in touch with the P&C team.

English and German lessons with native speakers

English is our main working language across the whole company. To help everyone to make the transition, we have regular training sessions in small groups led by a native-speaking English coach.

Having English as our everyday language has allowed our team to become even more multicultural and diverse and makes it easier to work across borders.

If you already feel comfortable with your English skills, we also offer German lessons led by a native-speaking German coach.

You can join the #misc-english-course or the #misc-german-course Slack channels and take part in one of the groups.

Hellobetter - Effective, individual, and flexible.

The signs that stress is controlling our lives and affecting our mental health can be big or small. With HelloBetter, you can take control and start looking after your health today. Register for one of their scientifically proven online courses and improve your own well-being. Please find the access details in confluence.

Guidelines

The guidelines section covers basic topics to find your way around thomann.io

Working time

Working hours, travel times and event days including overnight stay e.g. conferences, workshops, trainings in another location than your permanent residence are accounted for as a maximum of 10 hours.

Exception for car travel Here, the working time and the travel time must be logged separately. Please also enter the actual time value here. Here the working time may also be max. 10 hours. But the car journey is added on top and therefore a working day including the journey can have more than 10 hours.

When we work

We rely on self-organized groups of individuals that know when and how to get their best work done. A team also decides how much overlap they need to collaborate.

We aim for 40 hours a week (for a full-time employee). This helps us focus on what's important. Each team and individual know best when to work. We have no fixed schedule.

We emphasize a healthy routine for everyone. That includes having a life outside of work and getting a good amount of sleep. That's the best productivity hack you can get.

There may be exceptions, but they stay exceptions. We act proactive. If we exceed these hours regularly, we figure out the issue and solve it. That can mean recruiting more people, fixing a flawed process, or something else.

Working locations

Working at different locations within your country of residence is possible at any time. Please make sure that you have all the necessary conditions for your work at these locations e.g. strong internet connection.

Working from EU countries can be discussed individually at any time. Please contact your manager and the people & culture team to find a suitable solution.

Time Off

Holiday / vacation

You can take a vacation as spontaneously as you like - but keep the following rules in mind:

• Get the "go" from your lead person & team early on.
• Plan ahead. If possible: plan your vacation at least one iteration in advance.

Do not forget to

• Communicate your vacation to your team.
• Submit your vacation to kenjo.
• Set your absence note and add a public out-of-office appointment to your Google calendar. Guidelines at the bottom of this page.
• Make a vacation handover. You are accountable for ensuring that all tasks and issues have been handed over to your team.
• Cancel your appointments (you can do this automatically through your out-of-office appointment in Google calendar.

Christmas Business

The period from October to January is clearly the period with the highest revenue in the store.

Even during the Christmas period, we have to ensure that all teams deal with critical bugs and problems promptly (on working days).

Our teams ensure this through self-organization.

Christmas Eve and New Year’s Eve

For the hourly calculation on these days, please look in Kenjo on the respective day and submit the holiday according to our guidelines.

Overtime compensation

Same guidelines as for vacation apply. We offer overtime compensation as time off.

Important: Kenjo does not offer the option to convert overtime into time off by yourself. If you want to have it converted, please contact your lead/manager. Only after the conversion, you can request overtime compensation via Kenjo. Otherwise, unfortunately, the tool will track negative hours for overtime compensation.

Illness / Absence

First of all: If you're feeling unwell due to physical or mental illness, no one expects you to work. Don't hesitate to call in sick, whether it's due to physical health, mental health issues or your period.

If you need an overview of people on vacation or absent, you can use the calendar view in Kenjo or subscribe to the Kenjo calendar feed with your own calendar app.

Process

• Send a message to your lead person (before the daily).
• Cancel your appointments on that day.
• Let your lead person know when you're back.
• If you are absent for a longer period of time, make a handover with your team if possible. You can also set an out-of-office appointment in your Google calendar that automatically declines your appointments.

Formalities

The submission of the eAU (certificate of incapacity for work) is mandatory after day 3.

Important: If you are sick on a Friday and also on the following Monday handing in an AU is mandatory. This is independent of feeling well over the weekend or having a different illness on said Monday.

If you report your illness via Kenjo, please always note whether an eAU is available or not. It's no longer necessary to upload an AU to Kenjo. The AU is now requested digitally by us from your health insurance companies. However, you still have the right to have the doctor provide you with the AU certificate in paper form, should there be any technical problems. Please always have this certificate issued to you and store it for at least one month.

Child illness

We know that having sick children can be an extra burden for an individual to deal with on top of their usual work. To give a bit of credit to all the parents amongst us, Thomann.io grants its employees an additional 5 days of leave to take care of their sick children per year, per child. To hand a day in, please use the additional absence rule for the child's sick leave in Kenjo and note the number of days used, for example 0.5/5, and the name of the child in the comment field when submitting an absence request.

The days don't have to be taken consecutively, they can be taken individually. These days are only valid for children up to 12 years of age.

The first 5 days in a year that your child is sick, you can take care of them at home, without having to get a doctor's certificate, and we will pay your salary as normal, no worries.

For any day after that, Thomann.io won't pay your salary as normal: you will need to get a doctor's certificate and get your salary for those day(s) reimbursed by your health insurer. You can usually get around 60-70% of the salary back from your insurer.

Illness during vacation

The worst that can happen is to spend your vacation being sick. Therefore, you can call in sick during your vacation to get the lost vacation days credited back.

The process differs from the standard process:

• To get vacation days credited back, you have to get a doctor's attestation on day one
• You have to hand in the attestation in Kenjo and with your health insurance
• Also make sure to notify P&C about it, to have the days covered in the attestation credited back to you

This process goes for vacation within your home country and abroad. If you're abroad, you will have to visit a doctor there, too, on day one of your illness. You can look for more details on the website of your health insurance.

Special leave

Special leave is an essential aspect of our leave policy that recognizes the diverse needs and situations that you may encounter during your employment tenure. The purpose of special leave is to provide you with the flexibility you need to attend to extraordinary circumstances while maintaining job security.

For the following reasons we offer special leave:

• Death of a relative (1st degree: spouse, child, parents) - 2 days
• Wedding - 1 day
• Birth of the child (fathers) - 1 day (day of birth)

Do not forget to:

• Let P&C know that you are applicable for a special leave day
• Submit your special leave to Kenjo (use the special leave rule) --> also possible after your return
• Make sure to follow the basic vacation guidelines above

Communicating your absence

Don't forget to be transparent about your time off. While it's not necessary to mention the reason for your absence, it's important to communicate when you will be out of the office. Make sure to update your Slack status with an emoji like :palme: or use the predefined status and inform your contacts.

Set an out-of-office auto-response for your emails. Your auto-response should include the duration of your absence, who to contact as your substitute, or to whom the emails will be forwarded.

Not mandatory, but helpful: if you're able to, please also take care of this during long-term sickness.

Travels (booking and reimbursement)

Business trip travel expenses rules

Reasons for travel expenses for remote team members (even if living close to the office):

• Onboarding/offboarding in the office
• Workshops in the office
• Conference/training in your city
• Team events (2 times a year)
• Real business trip, errands for the office etc.

Voluntary office days, normal team meetings e.g. 1 x week or month etc. can be only be recovered through the income tax return.

Excluded: Employees who always go to the office (office contract) or receive public transport allowance.

Only kilometers travelled or tickets e.g. tram, bus, train can be reimbursed in the travel expense reports. Reimbursement is not possible without a ticket.

If a team member who does not go to the office regularly and only has a private annual ticket (i.e. no public transport subsidy from the company), they cannot claim the costs via the travel expense report. They can only deduct them via income tax.

Public transport allowance

An allowance on public transport costs is possible with the following conditions:

• You have an office contract or a hybrid contract (team members with a remote contract are not eligible).
• You must go to the office at least 3 out of 5 days per week, each month, to be eligible.
• The public transport allowance is up to 85 EUR per person per month. If your public transport ticket costs less than this amount, then you will receive that amount instead. Sounds like you? Then email Orga with your proof of purchase, and they will explain the next steps

Rules for train booking

• you have to book the train tickets yourself
• only 2nd class tickets
• choose Sparpreis tickets (not Flexpreis; Sparpreis is a good choice, because one still has the option to cancel the train ride, while that is not possible with Super Sparpreis)
  • to get the city ticket option enabled, please choose your real start and end locations, not just the main stations of a city (e.g. Berlin Brunnenstr. instead of Berlin Hbf)
• If possible, try to avoid traveling on Fridays. It’s a heavy commute day, therefore the probability of train delays and failure is higher. If you cannot avoid traveling on a Friday, please book a Flex Ticket one way. It’ll give you a little more flexibility with trains.
• always book a seat as well
• we strongly advise you to plan your trip well in advance to avoid high ticket costs and think your traveling plan through in order to avoid cancellation fees

Travel expenses reimbursement tool

After the trip you will submit the invoices for your tickets for reimbursement through the travel expenses reimbursement tool. All travel means apply - train, bus, taxi, flights, public transport - as well as travels by car and parking.

Link to the tool

For all employees of Thomann GmbH (the Headquarters) or partner companies (eg. Datadice, Sunlab, Coding Pioneers), the rules of the respective company apply. The thomann.io reimbursement tool is not meant for their use.

Meal allowance (Verpflegungsmehraufwand)

The daily meal allowance (Verpflegungsmehraufwand) only applies to travel with overnight stay. Please enter an honest count of the meals that have been paid for by the company (either through the hotel booking or team dinners, company events and alike). If all three meals in a given day have been provided to you by the company, you are not entitled to the meal allowance for that day.

Hotel bookings

Hotels will be selected and booked by the Orga-Team. The hotels are always booked with breakfast. Please inform the orga by email about your business trip.

The following information is needed:

• Place
• Date (arrival and departure)
• Note if no breakfast is required
• Possible allergies or other requirements (for example air conditioning in the summer, working desk in the room,...)

If possible, send hotel booking request to Orga-Team two weeks in advance.

Bahncard

There's a possibility for you to get a Bahncard. If you're eligible depends on the amount of roundtrips you're traveling cross-country (and for business purposes). Regional travel (e.g. Bamberg - Erlangen or within other metro areas) does not count for eligibility.

• Bahncard 25 (2nd class): 4 cross-country roundtrips per year
• Bahncard 50 (2nd class): 6 cross-country roundtrips per year

Consult your manager to estimate your necessary travels (e.g. take the last six months into account). When your manager approves one of the two options, purchase the respective Bahncard and hand in the invoice via the general reimbursement section of the travel expenses tool.

Team events

Requirements

• each team member should participate in up to two team building events per year (excluding events like yearly kickoff or open space).
• make sure at least one of your two events includes some sort of workshop/working together/reflection to become better in your day-to-day work.
• examples to use the events with your team/unit/community are: team building, onsite retros, design thinking, product workshop, dining, lasertag, a bbq boat etc.
• an event can be organized as a team, a unit, or a community, since not every person in our organization is part of a regular team.
• look left and right when organizing an event. Is there somebody working closely with you who’s maybe lacking a team? Invite them!
• we provide 100€ per person two times a year.
• not included in the 100€: travel & accommodation. Book your train and hotels as usual and fill out the travel expense tool.
• if relevant the team event should be held close to where the most team members are located, and must be within Germany.

Process

• Team events must be requested at least 4 weeks in advance.
• Choose an activity manager for the event from your announced team.
• Once you decide on the date and location for your team event (Berlin, Erlangen or Treppendorf/ Bamberg), the activity manager should create a Slack Channel with orga team (Meike, Iva & Lisa) (#teamevent-teamname)
• The orga team is committed to supporting you at every step of the way
• Booking, reservation and payment of the team activity is done by the orga team.
  • Exception: restaurant visits with hospitality receipts. Unfortunately, restaurant visits cannot be paid in advance. That is why the activity manager lays out the amount. The activity manager then submits the hospitality receipt to the orga team for payment after the event. Attention: Always ask for a hospitality receipt (Bewirtungsbeleg) at the restaurant. This is necessary for the payback. For the reimbursement send a scan of your receipt to accounting directly after the team activity has taken place. Thereafter, you are required to hand over the original hospitality receipt in paper form to the persons in charge in the offices Erlangen and Berlin or send it per mail to the orga team.
• Train and hotel bookings will be made as usual.
• Time tracking: put 10h of traveling into Kenjo or ask the person in charge at Thomann GmbH to put it in qtime (for Thomann GmbH employees). If the team event happens at your location of residence, track your normal maximum working hours (e.g. 8h standard)
• Once you had a great time, share 1-2 photos and a short description for everyone in #news-slackcast

Offices

You can always visit one of our offices. Be it Berlin or Erlangen or a trip to our headquarters in Treppendorf. If it's for day-to-day work, we recommend to commute to your closest office. If it's for onboarding, workshops, or other events with a higher purpose than "just work," there are no restrictions.

Be it onsite or remotely, make sure to connect with your team members regularly. Schedule coffee calls or have lunch together. We encourage you being you and making friends out of your colleagues. Check the travel guidelines for further information.

Remember, we are a remote first company and even if traveling for yourself might be easy, some team members may have long train rides or even have to take a plane.

Communicate your visit

When you plan on going to our offices in Erlangen or Berlin, make sure you add your visit to the respective office calendars. The calendar IDs can be found in our general thomann.io confluence space. This is especially important if you are the organizer of a larger workshop/group event in one of the offices.

Book a meeting room

You need to use one of the meeting rooms in our office?

No problem - let's make sure it isn't already booked and that it doesn't get booked over later. Please use the appropriate office calendar (Berlin or Erlangen) and create an event for the day you want to book your meeting room.

Please include event title:

• Your name
• Room name
• Start and end time of the booking
• e.g. "Mike / large Berlin meeting room / 9am - 6pm

Onsite Workshops

When planning onsite workshops, please take the following guidelines into account:

• onsite workshops must take place in either one of our offices in Berlin or Erlangen, or in the headquarters in Treppendorf. We do not offer budget for external locations
• if possible, contact our orga team 2-3 weeks in advance or as soon as possible. They can help you with meeting room availability and an overview on our workshop equipment
• our standard equipment in each office includes flipcharts, whiteboards, markers for both, a selection of stickies and pens, paper cards, and crepe tape
  • in case you deplete some mentioned items, contact the orga team to have them reorder what's missing
• if your workshop has a lot of participants or any other restraints (e.g. a classified topic), the orga team can help you book one of our offices exclusively for your planned endeavor

Personal data

If your personal data (e.g. address, martial status, bank account) changes, please follow the following steps to ensure a seamless update process for your employee file and salary information.

1. Update your profile in Kenjo.
2. Write an email to orga containing all updates.

Especially regarding banking information, it's important to inform proactively before the 10th of a month. This ensures that our tax advisor is provided with the correct data to handle your salary.

Creating new roles and hiring people

Identify the need

Determine the purpose and goals of the new position. Consider how the role will support the company's overall strategy, fill a specific skill gap, or help manage an increased workload. Consult with relevant stakeholders, including department heads and executives, to ensure that the new position aligns with the organization's needs.

Draft a job description

Write a clear and concise job description that outlines the responsibilities, qualifications, and expectations for the new position. Use industry standards and best practices to craft a comprehensive description that will attract qualified candidates.

Seek Manager approval

Before moving forward with the recruitment process, it's essential to obtain approval from the relevant manager or executive who will oversee the new hire. Provide them with the job description and explain how the new role will benefit the department or organization. Address any concerns they may have and be prepared to make adjustments as needed.

Determine the budget

Work with the finance department and the approving manager to determine the salary range, benefits, and other expenses associated with the new position. Consider factors such as industry norms, company budget constraints, and the level of experience required for the role.

Post the job

Once you have manager approval and have finalized the job description and budget, it's time to post the job. Talk with people and culture about available recruitment methods to attract a diverse pool of qualified candidates, including job boards, social media, and employee referrals. Make sure to communicate the urgency of filling the role. Some positions are nice-to-have, and it's okay to take some time to fill them. Some positions are super-urgent.

Define the hiring process

Work together with people and culture to define the hiring process, e.g. who will screen applications, who will be involved in technical interviews, and if there's a trial task. Also clarify, if part of the process will be onsite at any of our offices. Make also sure, people involved are aware of the process and have some spare time to be involved.

Secondary employment

It’s a common thing in our industry to have side gigs. Some people are musicians, some work for events, some freelance in tech, some have completely different ideas.

As long as you are 100% committed to your job at thomann.io, a secondary employment is possible.

Process

• Consult your lead and get their permission
• Contact people & culture for the official paperwork

Losing focus on your primary job repeatedly, however, might result in your permission being revoked.

Information and education

This section covers two topics:

1. our regular meetings that help you get all the information you need
2. different means of trainings you can use to learn something new or improve on skills

Our Year

Quarterly kickoffs

Each quarter has its own story. We're kicking off our quarters with half-day-kick-offs where all teams shortly present what they'll be working on in the upcoming months.

Assembly

Our all-hands meeting. Once a quarter, before our kickoff.

Open Space

A day for team-wide knowledge sharing. Bring in your own ideas and topics. The usual tracks are tech, product, meta, music. There'll also be workshops, hackathons, and team building. It usually happens in person.

Cyber Week

A staple in e-commerce nowadays. Around thanksgiving and black friday (end of November) online shopping goes crazy, and we're in the midst of it.

Christmas Business

October 15 marks the traditional start of Christmas business in e-commerce. This is when we enter the phase of showing our prettiest faces and a polished user experience.

Team/Unit Events

Get to meet your peers, your team members, your unit members. Check with your lead or your team on how and when to organize events. Feel free to rent a boat on Spree river, visit a drip stone cave, or go for Mario Kart like go-kart. Check the guideslines section for more information.

Assembly

2024 will see the Assembly as a quarterly all-hands event, conducted remotely and recorded for all team members that might miss out:

• If you are working on the day of the Assembly, participation in the call is mandatory
• If you're off that day, watch it, as soon as you're back at work

The Assembly consists mainly of these parts:

• Thomann GmbH company updates
• Division recap of the past quarter (from an organizational perspective, i.e. newbies, leavers, badges)
• Thomann.io organization updates (i.e. handbook updates, communities, events)

The Assembly (video & slides) is posted to #io-team-all once it has taken place. If there are questions to any of the Assembly's topics, use the post's thread. An answer will be provided there.

Important: participating in/watching the Assembly is mandatory because it contains relevant information for every team member.

In #io-team-all you find all previous Assemblies bookmarked as well.

If you need to contribute to the Assembly, there are some guidelines available in Confluence.

THOMANN.IO Blog

Every team member is allowed to write blog posts for thomann.io. If you have an interesting topic, or you want to introduce your team, feel free to write a blog post.

Since our team's take care of their recruiting process and of creating job ads, it's recommended to have a blog post introducing your team. And remember to update regularly.

If you want to write a blog post, just send a message to our culture lead for credentials to contentful (the CMS behind the blog).

Blog posts need the following structure:

• title
• teaser test (one sentence or so)
• the text (markdown preferred)
• an image
• an author

You can find the login information in Bitwarden. It's shared with every team member on organizational level.

Trainings

Personal trainings

So, you want to skill up and learn some new things? Great! As part of our learning & development opportunities, each team member is eligible for a 1,500 EUR (net) training budget per year.

There are a few restrictions, however:

• It is something that will help you grow within your role and expertise
• Your manager approves it
• You are permanently employed, i.e. not a working student, intern, or similar
• For trainings: they need to take place in your country of residence and not require air travel. If one of these two does not apply, your manager has to consult your unit's director for approval
• For conferences: we are aware that the best technical conferences might take place in a different EU country. If you're choosing such a conference, book it in advance (at least 2 months when possible) that we can request a A1 form from your health insurance (required for business travel)
• You are not allowed to divide your budget up infinitely. In total, you can use three working days for trainings/conferences and should choose a means of transportation that enables you to work while traveling to/from the location
• Please track your budget

After that, the process is fairly simple:

1. Write an email to our orga team, with your manager in CC, and explain which course you want to take/which book you want to buy/which conference you want to attend/etc.
2. Orga will book it on your behalf. In case they are unable to book it on your behalf, we may be able to reimburse you after you purchase it yourself, but please talk to us about this option first.
3. Once you've completed your training, feel free to share some content & insights in our workshops & learning shared drive.

Additional external trainings need approval from your unit lead and the respective director.

Working students are not entitled to the above-mentioned further training budget. However, we are happy to cover the costs of specialist books or magazines, for example, which contribute to the student trainee's work at thomann.io.

Happy learning!

General workshops

From time to time, different workshops for different audiences will be offered. Some formats we do on a regular basis are for example workshops on how to give/receive feedback or introductions to design thinking or devops. There is a shared drive pinned to #news-slackcast where team members can share material from interesting workshops for everyone. If you have something, put it in there. Create a folder that follows the format YYYY-MM-DD-workshop-title-trainer-name and move your files in it.

Internships

Internships in other departments of Thomann are possible at any time and explicitly desired. Possible departments are logistics, hotline, store, purchasing, etc.

Why would I do that?

• Take a look behind the store development
• Get to know other colleagues, departments and working methods
• Understand the company, processes and procedures better
• See what our customers do outside the store but also tell others what we are working on at thomann.io and how we do it
• Alignment: that we want the same as everyone else: Inspiring and enabling all people to speak music, everywhere.

Process

• Talk to your manager about a suitable internship timeframe (e.g. when your team's workload is low)
• Reach out to P&C with your agreed timeframe
• P&C will connect you with the internal contact or coordinate with Thomann, if required
• The assigned contact person will help to organize and coordinate the internship

For any questions, contact P&C. They look forward to supporting your internal internship.

After everything is organized, you take care of your travel to the headquarters.

Educational leave

Educational leave lets employees take time off for professional and personal development. Rules vary by Bundesland, and we offer it as required by law to support our team's personal growth. For more details don’t hesitate to contact P&C.

E1T1 (Each1Teach1)

E1T1 is a format where colleagues can share their knowledge with and practice public speaking in front of colleagues. You can talk about any topics related to Thomann, or about technology. You can decide how you want to do it (a presentation, a workshop, a talk, etc.). The duration is typically one hour, and it takes place monthly on the last Friday. It's meant as a voluntary format to spend lunch together. Here is the link to the backlog of topics. Please contact people and culture, if you have a topic or questions.

Tools

Our philosophy about tools - new or current

As for everything we do, structure follows strategy. Our tools have to contribute to solving our day-to-day challenges and not be challenges themselves.

Introducing new tools

1. Check, if we already have a similar tool in use, or already an account with the tool you'd like to introduce. This can be done with the finance/BizAd people.
2. If there's a new tool you need for a project make sure it is GDPR-compliant. It might be necessary to have a contract data processing.
3. Next it is mandatory to request a company-owned account from tooling@. After they created an account, they will provide access to you. It is not allowed to store company-related data in a personal account.
4. Make it viewable for every stakeholder of your project, e.g. other team members, people from other Thomann departments. Viewable should also mean secure: protect the link with a password where possible or create user/guest accounts. This will help us to protect data and control who has access.

Slack

Slack is our main communication tool. You can reach every team member of thomann.io via Slack.

Etiquette

Using Slack can become confusing from time to time. That's why we try - especially in channels with more than two people and various topics - to answer questions in threads. This helps to keep the channels clean and to switch context between topics more easily.

Asynchronicity

Slack helps us to be very flexible in how and when we work. Therefore and due to other reasons (e.g. meetings, deep work, workshops) it might occur that team members do not respond immediately, and it's not expected from you that you respond immediately. Just make sure you respond to messages in a timely manner once you are available.

In situations where you need very urgent help, it's better to use channels such as #tech-dev or one of the support channels mentioned below to ask for help. This will increase the crowd you are reaching.

Open channels by default

Our Slack channels are open by default. If you’re unsure, whether you need a private channel, check these guidelines.

Private channels can be created when

• you need a safe space for a team or organizational unit/division, e.g. each of our teams usually has a public channel for requests and a private channel to handle day-to-day work, discuss conflicts, or hold retros
• the channel is used to work on and communicate classified information, e.g. financials or personal data of our employees
• the channel is used by two team members maximum, e.g. to collect 1:1 topics

Channel naming

To make it easier to search through channels and organize them, there is a naming scheme in place (introduction 01/2024). Please stick to this scheme when creating channels and apply it to channels that do not yet use this scheme.

The naming scheme uses prefixes, followed by a dash, and the channel topic: prefix-topic

Prefixes

• io- applies to general company-internal channels, reporting line channels, and office channels, e.g. #io-berlin, #io-managers, #io-team-all
• division- applies to channels that gather members of one division , e.g. #division-organization, #division-data
• unit- applies to channels that gather members of one unit, e.g. #unit-shop-engineering, #unit-product
• team- applies to all publicly available team channels, e.g. #team-flavortown, #team-bk
• community- applies to all community channels, e.g. #community-diversity, #community-wiki
• tech- applies to all public & general engineering channels, e.g. #tech-dev, #tech-talk
• data- applies to all public & general data channels, e.g. #data-gcp-alerts
• prod- applies to all product-focused channels, e.g. #prod-review
• proj- applies to all project-focused channels, best case temporary, e.g. #proj-cyberweek
• 1on1- applies to channels that are used for 1on1 topic collections, e.g. #1on1-jöran-ralph
• recruiting- applies to channels dedicated to recruiting a new role, e.g. #recruiting-it-security-engineer
• workshop- applies to channels used for organizing and conducting a workshop, e.g. #workshop-pc-and-finance
• thomann- applies to all channels that connect us to the headquarters, e.g. #thomann-universe
• support- applies to all channels in which team members can get support, e.g. #support-opsteam
• news- applies to all channels used to share information, e.g. #news-slackcast
• event- applies to all channels used for event organization, e.g. #event-openspace-2024
• misc- applies to all general channels with no specific business focus, e.g. #misc-music

If you find a prefix missing, feel free to add it to this list.

Important channels

#io-team-all and #news-slackcast

#io-team-all is used for must-have/must-know information. Announcements made in this channel should always use the @Channel mention. Ask yourself: does everybody need to have this information right now?

#news-slackcast is used for should-have/should-know/nice-to-have information. For example all-over business context, information on workshops/team events that happened, progress of team projects, new people starting, old people leaving... Information provided here should either be posted without a mention or only use a weaker form such as mentioning a single team or @hier

Both channels are standard channels every newly added team member should join. If you haven't joined yet, please do so.

#thomann-universe, #tech-news, #tech-talk, #misc-coffee-time and #prod-bauchpinselei

#thomann-universe is used to connect all team members and all guests. It has no real communication purpose other than being able to contact all people we have in our slack workspace, regardless of being guests or workspace members.

Use the #tech-news channel to share important announcements that are relevant to all developers. This includes important code changes, accepted rfcs, patch day information and many more. All other questions and discussions that are relevant to all developers or where it's not clear which developer to ask are best placed in #tech-dev.

Use the #tech-talk channel if you stumbled upon interesting news in the tech world outside thomann.io that team members could be interested in.

If you find a really positive customer feedback, provide it to everybody in #prod-bauchpinselei.

#misc-coffee-time is a standard channel that helps you to connect to other team members. Every monday our coffee bot will match a new pair of team members to have a call in the current week.

Do not use @channel or @here mentions in these three channels. If you have important news that justify pinging everyone better choose #io-team-all or #news-slackcast.

Support Channels

Any questions regarding our infrastructure or how to track data and receive it? Both channels help you to quickly connect with team members of our operations and of our data team. Remember: there are no stupid questions. If you’re asking yourself a question, chances are high someone else can also profit from an answer.

#support-opsteam

This channel offers you a simple form for your request. Please try to provide as much information as possible and as little as needed. Opsteam will look into your issue and report back in the channel. All information is also tracked in an aligned Jira issue. The status of your request in the channel is visible at any time.

It is also possible for other team members to jump into the conversation and help out. Feel free to do this! Your collaboration is very much appreciated...

#support-datateam

In #support-datateam you can use @datateam for urgent requests. If you have a specific request it's best to put it in a Jira ticket.

#support-jira

It's our channel for all things Atlassian. Use this channel in case your team's coach can't help. In here the opsteam and our coaches work hand in hand. Please read the channel's canvas for more details.

Guests and Slack Connect

When working with externals in Slack, please follow these guidelines:

• if externals use Slack themselves (i.e. at their company), invite them to the required channel(s) via Slack Connect. Admins on both sides will have to approve this request
• if externals do not use Slack, invite them either as single channel or multichannel guest, depending on the number of channels they need to be part of
• you must not add externals as full member due to the potential security risk

Slack admins

If any of your requests need admin approval, Slack will notify this group. In case you have an urgent request, you can find all admins via the @admins handle in Slack.

Google Workspace

Our documents, spreadsheets and presentations are created with the tools by Google.

Email

Google Workspace provides you with access to your @thomann.io inbox. When you start your job with us or change your role, make sure you adjust your signature. The signature template can be found here.

• The signature is HTML, copy&paste it by using “select all/cmd+a shortcut” and paste it into the signature field of gmail. Apple Mail works if you uncheck the "use standard fonts" checkbox. It's preferred that you use Gmail directly, though.
• There are a couple of placeholders (name, role, phone, email, and external company) - make sure you fill what’s applicable and delete what’s not.
• For our folks employed at CP or Sunlab - due to legal reasons, you need your real company name behind your role. Put it in brackets, e.g. (Sunlab GmbH)
• Set the signature for new emails and answers/forwards

Calendar

We use Google calendars for our appointments. Make sure you take care of your calendar, so other team members can rely on booking appointments with you on free slots. Find more information about appointments in the how we work section of the handbook.

If there's a sharing issue with one of our calendars, you can find the calendar IDs for manual integration in Confluence.

Sharing documents & Google groups

There are some shared drives, e.g. for presentation templates. Our preferred way of collaborating on docs is to store them in shared drives that can be accessed by everyone that needs access and belong to nobody in particular. To simplify sharing (but also invites or emails to larger groups) make sure you use groups. This helps us to manage access and grant transparency way better than on an individual level. If you need a new group and don't have rights to create one yourself, create a ticket for the ops team via Jira.

An example: if you onboard a new team member and at it to a specific group, e.g. engineering, the calendar will automatically show all appointments were this group is invited.

Kenjo

Kenjo is our people and culture tool. It's used for all people-related tasks:

• requesting vacation
• calling in sick
• setting and tracking unit/community/team/personal goals
• download paychecks
• etc.

You will get an introduction to Kenjo during your onboarding or when you switch to a role with more rights within the tool. If you need a refresh at some point, please contact people and culture.

Atlassian Cloud

Well, we said it. We work with Jira and Confluence in the cloud.

Jira

Jira is the place to collect tasks, projects, visions, bugs and user problems. Every member of thomann.io has access to check what we're working on and which steps we will take to reach our goals. It's also where you find the company backlog.

Jira must be used as a single source of truth for tickets and therefore for all work in progress and backlogs.

Company backlog

The company backlog displays all major projects across Thomann GmbH. It is used to make initiatives of our company's departments transparent to everyone and helps us to update each other regularly.

You can find the company backlog in Jira when clicking on "Plans" in the navigation.

Team Boards, product backlogs, and dashboards

Each team has their own board and backlog. Just search for the team's name in the board section, and you'll find it. Depending on the team's way of work it's either a scrum or a kanban board, some teams also have both. The team product owners are responsible for gathering the backlog items through the company backlog initiatives, through user research, or through our feedback hub. They refine them with the team and set a priority.

Status map

In order to simplify working together on projects, we agreed on a common simple workflow in Jira. Status usage is by definition.

All upstream statuses are intended for the ideation, information enrichment, prioritization (product strategy) of features or epics. The statuses in the downstream are for the implementing operational teams

Upstream

Downstream

Shared up- and downstream

Confluence

For internal documentation, Confluence is our single source of truth. Though, we try to be as transparent as possible with our employee handbook, there's a lot of project documentation and some internal processes (e.g. ordering new hardware) for which an employee-only wiki is the better tool.

Some teams might use tools like Notion, Lucid Chart, Miro, or whatever else fits for their current challenges. However, each team is obliged to make documentation accessible in Confluence. This means, when using different tools, make sure you share a link within the documentation, or better, look for a Confluence plugin to embed the information stored in a different tool.

Apps

There is a wide array of apps available for the Atlassian tools at their marketplace. Please follow this guideline when requesting one.

Bitwarden

Bitwarden is the password manager at Thomann.io. You can save personal and organization related passwords.

Personal Vault

You will get one personal vault named "My vault" where you can store your personal passwords.

Organization Vault

You will get one organization vault named "Thomann.io" where you can store and share group accounts with your team and in the organization.

Folders

A folder is for your own password organisation, that means that only you can see this folder structure.

Collections

A collection is like a team folder, every team will get one team collection where they can share passwords. If you put a password inside of this collection, all team members which are assigned to this collection will be able to see this password. One password can be in multiple collections, this means you can share one item multiple times with different teams if needed. The operations team is managing the collection structure, thus if you need something please contact the #support-opsteam channel in Slack.

Do I have to use this password manager

We do not check if everyone is using Bitwarden as a password manager but if you are storing organization related passwords somewhere you have to use it.

If you have further questions, please take a look into our tutorial video in our Bitwarden Confluence page or contact the operations team in the #support-opsteam Slack channel.

Miro

We use Miro as online whiteboard tool. If you work regularly with it, contact orga or the agile coaches for a user account.

Sharing boards

When sharing boards with visitors, always set a password and distribute it safely, e.g. with Bitwarden or our internal pastebin app. Don't let boards be open to public, even if you think it's hard enough to guess their urls.

IT Support

Internal (client) IT support, takes care about all client hardware, software and licences, helps you with your device problems. Click the headline to find more information and processes on the related Confluence page.

Our Responsibility

Thomann and our Environment

The environment and using sustainable resources is incredibly important to us. Here you can find out what Rock'n'Roll and nature have in common.

Whistleblower Protection Act

The Whistleblower Protection Act is a law that aims to provide legal protection to persons who report wrongdoing in their work environment. These grievances may relate to illegal activities, breaches of compliance policies, fraud, corruption or other serious offences. The law protects whistleblowers from possible negative consequences or reprisals from the employer.

You have the right to report ethical concerns without fear of retaliation anonymously at Hintbox.

Your report will be treated confidentially as required by law. You do not need to fear that your identity will be disclosed unless you give explicit consent or it is required by law. The Whistleblower Protection Act is an important tool to maintain integrity and ethics in our business.

Thomann.io encourages all employees to report ethical concerns and is committed to protecting them from retaliation. We believe that adherence to these guidelines will help ensure that our organisation is run ethically and legally responsibly.

Please do not hesitate to contact people and culture or your lead if you have any further questions about the Whistleblower Protection Act and the reporting tool. Your integrity and protection are important to us.

Communication & company language

Our company is becoming increasingly international, and we recognize the importance of effective and easily understood communication between our various team members.

To ensure clarity and integration, we use English as the default language for all written material and communication.

This move helps to break down language barriers and facilitate seamless communication between our international employees to promote efficiency and understanding within our organization.

Email name scheme policy

The default rule is that all company email addresses must follow the typical format: firstname.lastname@thomann.io

However, we’ve agreed on the following exceptions, which can be applied if requested by the individual:

• Preferred names for unisex names
• Cultural sensitivity
• Double names or very long names can be shortened

These are special cases that require approval on an individual basis. People and culture will review the request and decide if it’s feasible.

Audiences

Different pieces of information and a different density of content needs to be shared between various roles. Therefore, this page provides some guidelines on how to address different people and groups in the company.

If you're addressing a huge audience, e.g. the complete team, think about how to share information. It might make sense to create a handbook entry or a confluence page and just refer to it in a Slack channel.

If you're addressing stakeholders or higher management, it can be helpful to use a presentation or just share bullet points, and provide more information through a discussion.

If information is interesting for engineering or data people, it might be cooler to share them within a repository, e.g. how to set up and run an application. But think about dependencies: the more an application has, the better it might be to give an overview through a detailed confluence page.

Some people or groups from the headquarters are best reached via email or telephone. When calling or meeting, make sure to send around some minutes afterwards.

Business language

Working at Thomann.io or with Thomann.io can be quite challenging when not used to all the terms we're using on a daily basis. Be it definitions from software development, e-commerce metrics, or something about agile, there are words that can be overwhelming to stakeholders, especially when used repeatedly, e.g. in a heated discussion or in a review.

Therefore, we are working and constantly improving on a glossary to give definitions for technical terms. The glossary can be found here and is updated whenever we find situations that need a clarification of terms.

Important: as a team member, please be aware when others struggle to understand some terms you are using. If this is the case, add the term with a short German and English definition directly to the doc.

Consulting & supporting by asking questions

Here are some question techniques that go beyond open and closed questions. These can be helpful in feedback sessions, workshops, when advising colleagues, etc...

Solution- and resource-oriented questions

These are questions that focus on available resources and solutions. They encourage reflection on what worked before, what was tried, and which skills and chances are still hidden.

Example questions:

• How would the perfect [insert relevant context] look?
• When was it good? What was the significant difference?
• What is different when it’s working?
• Who could help you with this?
• Which of your skills are especially helpful?

Scaling/Rating questions

Scaling or rating questions ask individuals to evaluate something on a numerical scale, such as from 1 to 10.

Example questions:

• On a scale of 1-10 how proud are you of your work?
• Where do you want to be on this scale in two month?
• What needs to happen in order to come one step closer to 10?

Circular questions

Circular questions shift perspective by asking how others might view or react to a situation.

Example questions:

• How would your colleague describe the situation?
• What would your boss say if you behaved differently in that situation?

Hypothetical questions

Hypothetical questions are useful for exploring future scenarios, expanding understanding of a system, and considering potential solutions by removing current limitations.

Example questions:

• What if money/time is not a limiting factor? How would you handle this situation?
• If you knew you couldn't fail, what would you try?
• If the problem isn't solved in 6 months, what consequences would it have?

Paradox questions

They emphasize the problem which can help to bring up ideas for solving the problem.

Example questions:

• What needs to happen that your boss fires you?
• How can you manage to come even less motivated to work?
• What needs to happen so that the project definitively fails?
• How could you make sure that no innovation ever happens within your team?
• What is the most effective way to get completely ignored in meetings?

Changelog

For every change to the handbook, follow these steps:

1. increment the version depended on the size & impact of your change. If unsure, ask in the io-handbook Slack channel.
2. add the date of your change to the headline
3. per change, write a change note as unordered list item preceded with the section you updated (e.g. guidelines/secondary employment:)

v2.1.7 - May 26, 2025

• structure/within-teams: added further roles to better explain how our teams are structured

v2.1.6 - May 6, 2025

• added CODEOWNER file to the handbook repository (no content change)

v2.1.5 - Apr 30, 2025

• career/1on1s: new page with an example template for successful 1on1s between an individual contributor and their manager
• communication/questions: new page with exemplary question techniques to support peers

v2.1.4 - Apr 16, 2025

• guidelines/team-events: new channel based process (instead of activity form) to organize team events

v2.1.3 - Apr 2, 2025

• information and education/trainings: added net info to training budget

v2.1.2 - Mar 31, 2025

• career/feedback: added instructions for the BIO feedback method
• career/feedback: added instructions for the feedforward canvas method

v2.1.1 - Mar 19, 2025

• how we work/management: added information about the leadership learning path

v2.1.0 - Mar 17, 2025

• how we work/management: removed softskills for managers and added information about new management career path

v.2.0.13 - Mar 10, 2025

• how we work/psychological safety: removed lead community and replaced it with manager & peer in the important section

v2.0.12 - Feb 17, 2025

• tools/slack: added guidelines for Slack guests and Slack connect
• tools/slack: added information on how to contact Slack admins

v2.0.11 - Feb 17, 2025

• guidelines/onsite workshops: new page with guidelines

v2.0.9, v2.0.10 - Feb 13, 2025

• tools/slack: added new opsteam support workflow to Slack guidelines

v2.0.8 - Feb 5, 2025

• benefits: specified referral bonus guidelines for team members to better decide, if a candidate might be a fit

v2.0.7 - Feb 3, 2025

• added info regarding employee discount (how to communicate that you're eligible) in the benefits section

v2.0.6 - Jan 21, 2025

• changed training costs to training budget and added new guidelines accordingly
• added guidelines on possible email name schemes for company addresses

v2.0.5 - Jan 21, 2025

• added guidelines for christmas eve and new year's eve

v2.0.4 - Jan 13, 2025

• added guidelines on how to communicate absence, e.g. vacation or long-term sickness

v2.0.3 - Jan 9, 2025

• hallway radio is no English expression. Replaced it with office grapevine, meaning Flurfunk in German

v2.0.2 - Dec 3, 2024

• removed obligation to talk to your manager the contents of peer feedback
• added context to peer feedback that it is the starting point of the yearly career development

v2.0.1 - Nov 13, 2024

• introduced a changelog to the handbook
• updated readme.md to fit current Slack channel structure, not include redundant information, and clarify contribution guidelines to the handbook

v2.0.0 - Nov 12, 2024

• each topic that’s worth being found with one click now has its own menu item, e.g. there are no topics "hidden" on the overview pages of guidelines or information & education sections

< v2.0.0

For a change history of older handbook versions, please check the 2023 and 2024 assembly slides or the handbook's main branch commit history