Agile work made simple: methods and benefits

Agile work is an approach in which teams complete small units of work, review interim results on a regular basis and make adjustments immediately. This makes the approach particularly suitable for tasks where information and insights emerge gradually.

Agile work: key takeaways

  • Agile work means: completing tasks in small, reviewable steps and adjusting decisions regularly based on current interim results.
  • Core elements of agile work: short cycles, clear priorities, transparent workflows and consistent feedback.
  • Scrum and Kanban: the most widely used methods in agile work.
  • When agile work is most effective: when requirements evolve during the process, feedback is readily available and the team is expected to make decisions independently.

What does agile work stand for?

Instead of relying on one large overall plan, agile work is based on short work cycles that are reviewed continuously. This iterative approach creates a rhythm in which feedback can be incorporated at any time.

  • Kurze Zyklen: Arbeit wird in überschaubare Schritte geteilt.
  • Feedback: Ständig werden Zwischenergebnisse sichtbar und Rückmeldungen können einfließen.
  • Fortlaufende Verbesserung: Teams passen ihr Vorgehen und die Prioritäten regelmäßig an.
  • Offenheit: Aufgaben, Fortschritte und Hindernisse werden offen dargestellt.

How does agile work unfold?

Work is continuously prioritised, made transparent and adjusted based on the information available at that moment. This creates an approach that stays focused on the goal while allowing plenty of room for adaptation along the way.

  1. Clarify the goal or problem: Start with a defined goal or a problem that needs solving, for example developing an app.
  2. Prioritise the work packages: Gather the required tasks, assess them and sort them by importance.
  3. Plan short work cycles: The team decides which tasks will be tackled in the next cycle, such as a sprint or a week.
  4. Execute in small steps: The work packages are completed step by step. Dependencies and obstacles become visible early.
  5. Review results and gather feedback: Results are presented, checked and compared with user expectations or client needs.
  6. Adjust the approach (retrospective): The team reflects on what worked well and what did not, then adapts its way of working accordingly.

Which routines are typical in agile work?

  • Daily stand up: a short daily meeting of about fifteen minutes to set priorities and discuss any current obstacles.
  • Planning sessions: the team decides which tasks will be completed in the upcoming cycle.
  • Review or demo: the team presents interim results and receives immediate feedback.
  • Retrospective: a meeting focused on continuously improving collaboration and working methods.

Which methods are used in agile work?

The best known methods in agile work are Scrum and Kanban. They differ in structure but share the same goal: they make planning transparent, show how results become visible and ensure that feedback shapes the next steps.

Scrum

Scrum organises work in fixed iterations known as sprints, including defined roles, events and deliverables. A sprint lasts between one and four weeks and always ends with a result that can be reviewed.

Core elements of Scrum:

  • Fixed cycles: work is planned and completed in sprints.
  • Roles: Product Owner (prioritisation), Scrum Master (process), Developers (implementation).
  • Transparency: backlogs, goals and progress are kept visible at all times.
  • Feedback: each sprint ends with a review of the result and adjustments to the approach.

Scrum is especially suitable when requirements are dynamic, meaning they cannot be fully defined at the start and must be reviewed regularly.

Kanban

Kanban improves the flow of work without relying on fixed iterations. Tasks are shown visually on a board and move through defined process steps.

Core elements of Kanban:

  • Visualisation: tasks are displayed on a board so the current state of work is always clear.
  • Work in progress limits: each stage has limits to prevent overload and keep the flow steady.
  • Continuous flow: work moves through the process without fixed cycles.
  • Ongoing improvement: teams analyse bottlenecks and refine the workflow over time.

Kanban is particularly well suited to areas with continuous workflows, for example support, operations, marketing or HR.

What conditions are needed for agile work?

Teams that work in an agile way align themselves with the current goal, need the freedom to make decisions, require transparent workflows and rely on a team culture where open feedback is possible.

  • Goals and priorities: teams need a shared understanding of what they are working on and why. Priorities must be clear and reviewed regularly.
  • Decision making freedom: agility requires that the team can make decisions within defined boundaries.
  • Visibility of work and progress: tasks, status and current bottlenecks should be transparent at all times.
  • Cross functional skills: the team should cover as many required capabilities as possible.
  • Psychological safety: team members must be able to raise issues without fear of negative consequences. Only then will problems, mistakes and obstacles be shared openly and resolved.
  • Stakeholder involvement: feedback from customers, users or subject matter experts must be available and must genuinely influence decisions.

Examples of agile work

Example 1: Scrum – Developing a New Filter Feature

A SaaS provider runs a booking platform for seminars and training sessions. Customers regularly request faster filtering by criteria such as duration, format, or location.

Way of working:

  • The product team works in two-week sprints.
  • The sprint goal is an initial working filter for three criteria, without final design.
  • Filter selection and result logic are implemented as separate work packages.

Result after two weeks:

  • A simple, working filter panel for format (live / online), price range, and date.
  • The interface is not final, but fully functional and testable.
  • Users can filter real courses in a test environment and give feedback.

Outcome:

  • The team learns which filter combinations matter most to customers.
  • Technical feasibility is clarified before complex design begins.
  • Feedback is based on a real, working prototype.

Example 2: Kanban – Improving a Marketing Campaign Workflow

A marketing team manages ongoing campaigns for several product areas. Without a clear structure, tasks often pile up in the review stage, causing delays in releases.

Way of working:

  • The team introduces a Kanban board with the columns “Briefing”, “Concept”, “Creation”, “Review” and “Finalisation”.
  • The “Creation” and “Review” stages have WIP limits of three tasks each to make bottlenecks visible early.
  • Campaigns are planned as individual tasks, such as “create LinkedIn visual” or “improve ad copy”.

Result after four weeks:

  • The average turnaround time for a standard campaign element drops from twelve to seven days.
  • Significantly fewer tasks pile up in the review stage due to enforced WIP limits.
  • A graphic design bottleneck becomes visible and can be addressed through prioritisation or short-term support.

Benefits:

  • Campaigns launch more reliably and on time.
  • Capacity gaps are identified earlier and handled proactively.
  • The workflow becomes more stable and predictable without additional meetings.

{{onpage-cta}}

Trusted by 1000+ innovative workplaces

With PULT you can see which team members are in the office and where they are sitting. Make agile work easier with PULT.

FAQ

Have questions?

What does agile work mean in simple terms?

Agile work means handling tasks in small steps, reviewing interim results regularly and adjusting the approach whenever needed. The goal is to respond more quickly to new information or changes.

Why is agile work used?

Agile work is particularly useful in situations where requirements are not yet fully defined or change frequently.

Which methods are part of agile work?

The most commonly used methods are Scrum and Kanban. Scrum works with fixed iterations known as sprints, while Kanban manages work through a continuous flow and limits on parallel tasks.

Do you always need sprints for agile work?

No. Sprints are part of Scrum but not necessary for every team. Kanban and other agile approaches work without fixed iterations and rely on continuous flow and ongoing optimisation.

Is agile work possible outside software development?

Yes. Agile work is used successfully in product development, marketing, HR, operations, customer service and many other fields.

Which benefits does agile work offer?

The most common advantages include faster feedback loops, fewer missteps, better prioritisation, greater transparency within the team and results that become visible continuously.

About author

Isolde Van der Knaap

Hybrid Work Enthusiast and Account Executive

At PULT we're designing the future of the hybrid workplace for companies and their employees. Focused on SME and mid market customers in Eruope, I'm working on everything from Customer Discovery to Onboarding. I'm very passionate about new work and moved to Hamburg in 2024 even though I'm originally from France.

Resources

Learn how to run better workplace operations

Visitor Management

Organizing an Event: Checklist, Permits & Legalities 2026

If you organize an event, you now bear more legal responsibility than you did just a few years ago. New requirements for safety documentation, GDPR obligations regarding participant data, and changes to liability rules mean that event planning has become a task where relying on an outdated checklist can quickly become costly.

Organizing an Event: The Basics

  • Public events involving a large number of people are subject to a require a permit in Germany: Depending on the state and the type of event, applications must be submitted to the relevant authority at least 12 weeks in advance
  • Since the stricter requirements took effect in 2025/2026, event organizers must actively maintain their safety documentation: In the event of a claim, anyone who cannot provide complete documentation bears the burden of proof, regardless of whether there was any fault
  • The GDPR applies to participant data when organizing an event, and specifically to event photos and video recordings as well: Without explicit consent or a documented exception, substantial fines may be imposed.
  • Event management feature: With PULT, companies can coordinate corporate events, room scheduling, and attendee management all within a single system, directly integrated with Personio, HiBob, MS Teams, and Slack.

What permits do I need before organizing an event?

As soon as you start planning an event in Germany, you’ll encounter a complex web of regulations that vary depending on the state, the type of event, and the number of attendees. The key regulations include the Public Gathering Venues Ordinance, GEMA, and guidelines from the public order office.

  • Your city or town’s Public Order Office: The first point of contact for public events. The Public Order Office generally approves the event and coordinates with other authorities as needed. Private corporate events with a fixed guest list held at an approved venue do not require a separate permit from this office
  • Department of Streets and Green Spaces (also known as the Department of Civil Engineering or the Department of Urban Planning, depending on the city): You can apply here for a special use permit for events on streets, squares, or in parks. The exact name of the agency varies by municipality. The quickest way to find the right contact is to search for “special use permit for events” on your municipality’s city portal. Many municipalities now bundle this application in the Servicekonto Deutschland
  • Business Licensing Office: If you sell food or beverages, you need a temporary permit under the restaurant regulations of the respective state. This is a separate application, independent of the event permit.

Three additional points that often come up too late in the planning process:

  • GEMA: You must register music that includes GEMA-licensed tracks in advance at gema.de, whether performed live or played from a recording. The fees depend on the size of the event and the venue area.
  • Regulation on Public Gathering Places (VStättVO): For events with 200 or more people, the relevant building authority will verify whether the venue is licensed as a public gathering place. Clarify this in advance with the venue’s landlord, because as the organizer, you are jointly liable if the operating permit is missing or has expired
  • Fire Department and Public Health Department: For events featuring stage setups or food service, the Public Order Office often requires a fire safety plan and a hygiene plan. Make sure to get written confirmation that this applies to your event.

For all applications for which your municipality offers an online portal, the following applies: The Servicekonto Deutschland consolidates many of these forms. Start the application process at least 12 weeks before the event.

What has changed for events as a result of new safety regulations and the reversal of the burden of proof?

DGUV 115-002 sets forth safety requirements for event and production technology and applies to all events where technical equipment such as stages, lighting, or sound systems is set up. Starting in 2025/2026, authorities and courts expect event organizers to actively maintain their safety documentation rather than compiling it only upon request.

This means that risk assessments, evacuation plans, protocols for briefing service providers, and participant lists must be fully documented. If you cannot present complete documentation in the event of a claim, the burden of proof falls on you. A structured documentation system in place before the event should therefore be considered a requirement that you must comply with.

How do I comply with the GDPR when organizing an event?

As soon as you register participants, you are processing personal data and therefore need a legal basis under Article 6 of the GDPR. For corporate events, this basis is generally derived from legitimate interest. In this case, the data may not be used for purposes beyond the event and must be deleted after 90 days at the latest. The only exception to the deletion period is tax-related retention requirements.

Things get more complicated when it comes to event photos and video recordings:

  • Portraits and identifiable individuals: Publication is prohibited without express consent, even in the case of seemingly harmless group photos
  • Panoramic photos of large crowds: In such cases, a legitimate interest may apply, provided that individuals are not recognizable.
  • Online events and recordings: If you record events or meetings , you must inform participants in advance and obtain their consent. Starting a recording without prior notice is a violation of the GDPR.

When registering, provide a consent form that explicitly asks for permission to take photos and record videos. The same rules apply to hybrid events—that is, formats in which some participants join remotely—with the addition of recording requirements under data protection law.

Organizing an Event Step by Step: The Checklist

What tools can help with organizing events?

When it comes to organizing your event, three categories of tools cover the most important planning areas: tools for checklists and risk analysis, online portals for submitting official applications, and office management platforms for room scheduling and attendee management.

  • Checklists, AI: Use our event checklist and consult an LLM (Claude, Gemini, ChatGPT, etc.) to research the local and municipal requirements or guidelines specific to your state, as these cannot be summarized in a single, universal list.
  • Online permit portals: The Servicekonto Deutschland and municipal application portals allow users to submit permit applications via browser-based forms. However, availability varies by state.
  • Office management platforms with event features: A direct link between event planning, room management, and attendee management saves you the hassle of back-and-forth coordination.

PULT combines room booking, guest management, and catering into a single platform. You can book rooms, filter by capacity and amenities such as projectors or whiteboards, reserve areas on the interactive office map for your event, and add catering directly during the booking process. 

  • Rooms, catering, parking, and guest workstations—all in one booking.
  • Guests check in at the kiosk, and the host immediately receives a notification in Slack or Microsoft Teams.
  • At the reception desk, guests sign NDAs, photo release forms and receive a visitor badge and privacy notices.
  • In an emergency, PULT generates an Emergency Export of all currently present individuals at the push of a button.
  • The weekly planner shows in advance how many employees will be in the office on the day of the event, so that room planning and space utilization can be coordinated.

{{onpage-cta}}

Office Insights

Workforce Analytics: Definition, Key Metrics, and EU-Compliant Implementation by 2026

Workforce analytics refers to the analysis of personnel data to manage headcount, productivity, and workforce planning. HR teams use this method to support personnel decisions with data. Starting in August 2026, the EU AI Regulation will tighten requirements for AI-powered HR analytics and mandate specific structures.

Workforce Analytics: The Basics

  • Workforce analytics is the quantitative analysis of HR data—such as turnover, absenteeism, headcount, and office utilization—to derive actionable recommendations for workforce planning.
  • Key metrics for workforce planning analytics include turnover rate, time-to-hire, absenteeism rate, office attendance, and team-level productivity metrics.
  • The EU AI Regulation classifies many HR analytics systems as high-risk AI starting in August 2026, imposing obligations regarding disclosure, human oversight, and data protection impact assessments.
  • PULT provides the data foundation for workforce analytics in hybrid teams—including attendance, desk utilization, and room bookings—and thus complements traditional HRIS systems such as Personio or HiBob.

What is workforce analytics, and how does it differ from people analytics?

Workforce Analytics focuses on the quantitative aspects of the workforce. It centers on headcount, productivity, turnover, and workforce structure in medium-term planning. People Analytics takes this a step further and also examines behavior, engagement, and collaboration based on qualitative data. HR Reporting, on the other hand, provides only retrospective reports without a forecasting component.

workforce analytics

In day-to-day work, these two areas are closely intertwined. When you implement your own workforce analytics, you create the data foundation for people analytics and the overarching workplace management.

Which metrics are suitable for workforce analytics?

Workforce Analytics uses metrics such as turnover rate, time-to-hire, absenteeism rate, office utilization, headcount trends, and others, which are regularly collected and analyzed. Together, these metrics provide an overview of how the workforce is evolving and which areas of the company are over- or under-staffed.

What tools are suitable for workforce analytics?

Workforce analytics tools can be divided into three layers. An HRIS layer as the data core (Personio, HiBob, Workday), an analytics layer for evaluation (Visier, Tableau, supplementary HRIS modules), and an office layer for attendance and space data in hybrid setups. The right combination depends on company size, data architecture, and EU compliance status.

When making your selection, consider the following five points:

  • Hosting region: EU hosting with a data center in Germany or elsewhere in Europe.
  • API Capability: Interfaces with HRIS, time tracking, and office management systems to eliminate data silos
  • EU AI Act Status: The provider documents whether and how its tool falls under the category of high-risk AI
  • Level of detail: Customizable KPIs and freely configurable dashboards
  • Office database: Attendance data, room and workstation reservations as well as visitor management
Tip: PULT Workplace Analytics includes this office layer and feeds attendance data, desk utilization, and room bookings into your workforce analytics pipeline, which can be combined with Personio or HiBob.

What does the EU AI Regulation 2026 require of HR analytics systems?

According to Annex III of the EU AI Regulation, an HR analytics system is considered high-risk AI as soon as it automatically supports personnel decisions. These include recruitment, promotion, termination, and performance evaluation. As a result, many workforce analytics functions are subject to strict requirements as soon as algorithms independently generate recommendations for or against individuals.

What requirements will apply to HR analytics systems as of August 2, 2026?

The high-risk classification gives rise to four key obligations for new systems:

  • Risk Management and Technical Documentation in accordance with Articles 9 through 11 of the EU AI Regulation
  • Human oversight for every decision involving personal data, not just at a later stage
  • Data Protection Impact Assessment pursuant to Article 35 of the GDPR, plus a Fundamental Rights Impact Assessment pursuant to Article 27 of the EU AI Act
  • Co-determination by the works council pursuant to § 87(1)(6) of the Works Constitution Act (BetrVG) in connection with any introduction or adjustment

How can I ensure that my workforce analytics setup remains compliant?

You can ensure compliance by clarifying your data architecture and processes before purchasing a tool. This involves five key points:

  • EU Hosting: Servers located in the EU, documented data processing.
  • Purpose limitation: You must document in writing which data you are analyzing and for what purpose.
  • Human final decision: No algorithm makes the final decision regarding hiring, termination, or promotion.
  • Disclosure: You proactively inform employees about what data is collected and how it is analyzed.
  • Involve the works council: A works council agreement fulfills the requirement for employee participation.

How to Build a Future-Proof Workforce Analytics System

Workforce Analytics provides you with a quantitative overview of your workforce, from headcount forecasts and turnover to office utilization.

Starting in the fall of 2026, the EU AI Regulation will require specific frameworks for high-risk AI, documentation, and human oversight. With PULT, you can meet these requirements while still gaining reliable data for your workforce planning and site strategy.

  • PULT Workplace Analytics provides real-time attendance, desk, and room data as a data source for workforce analytics.
  • Native integrations with Personio, HiBob, Microsoft Teams, and Slack, so all your HR data is centralized in one place.
  • EU hosting and ISO 27001 certification as the basis for your GDPR and EU AI Act documentation.

{{onpage-cta}}

Office Insights

Micromanagement: Consequences, Legal Risks, and the Path to Controlled Delegation

Micromanagement refers to a leadership style in which supervisors closely monitor their team’s tasks and constantly intervene. The consequences range from demotivation and resignations to legal risks arising from organizational negligence. However, by reducing micromanagement and delegating effectively, leaders can improve team performance while simultaneously reducing their own liability risk.

Micromanagement: The Basics

  • Micromanagement is a leadership style characterized by excessive attention to detail and constant interference in the team's tasks. Typical consequences include demotivation, a decline in personal responsibility, and above-average turnover rates.
  • Signs of a micromanaging boss include constant status updates, nitpicking over routine phrasing, requiring everyone to be CC'd on every email, and approval loops for trivial decisions.
  • Micromanagement carries legal risks because unclear responsibilities can lead to organizational negligence, and excessive monitoring of employees may violate § 26 of the Federal Data Protection Act (BDSG).

PULT is an all-in-one office management software solution that provides executives with a data-driven overview of hybrid teams through Office Insights, desk booking, and visitor management, without the need to micromanage operational details.

What is micromanagement, and how can you tell if you or your boss is doing it?

Micromanagement is a leadership style in which supervisors constantly monitor their employees’ performance and constantly interfere in their decision-making. Engaged leadership is clearly different, as it sets clear expectations for the outcome but leaves the path to achieving it open.

From an employee's perspective, the following patterns become particularly evident when a supervisor engages in micromanagement:

  • Routine work is proofread and the wording is fine-tuned—something that should have been done long ago
  • You'll be copied on every email
  • Independent decisions are subsequently called into question
  • We receive several status requests every week, even though clear deliverables have been agreed upon

If you are a manager yourself, ask yourself whether the following statements apply to you:

  • You systematically proofread your team's documents before they leave the office
  • You have routine decisions notified to you before they are implemented
  • You step in whenever tasks aren't handled the way you would handle them yourself
  • You ask for status updates more often than your team can deliver results

If you answer "yes" to several of these questions, it's a clear sign that your leadership style has slipped into micromanagement.

{{hint-box}}

What are the consequences of micromanagement for the team and the company?

The consequences of micromanagement affect both the team and the company:

  • Increased willingness to resign and rising turnover
  • Declining personal responsibility and innovative spirit within the team
  • The risk of burnout among employees is constantly monitored
  • Poorer strategic decisions because managers are bogged down in operational details
  • High follow-up costs due to recruiting, onboarding, and knowledge loss

Studies on willingness to quit, such as the Gallup Engagement Index, consistently show that micromanagement is one of the most common reasons for changing jobs. In addition to the human and economic consequences, the legal risks carry particularly serious weight for German companies.

What legal risks does micromanagement pose for managers?

The legal risks associated with micromanagement are rarely mentioned in HR practice, but they are substantial and affect three areas.

Organizational failure resulting from micromanagement

When a manager makes all decisions on their own, lines of responsibility become blurred. If damage occurs, it is difficult to determine clearly who failed to fulfill which duty. The case law of the Federal Court of Justice requires that tasks, authority, and responsibility be clearly assigned. Micromanagement undermines precisely this requirement.

Employee Data Protection under Section 26 of the Federal Data Protection Act (BDSG)

Close monitoring of employees, such as continuous screen monitoring or constant activity tracking, may violate employee data protection laws. Monitoring measures must be proportionate and based on a specific reason.

Delegation as a form of liability protection

A properly documented delegation of authority protects the manager in the event of a claim. Three steps ensure its legal validity:

  • Assign the written assignment , including specific expectations regarding the outcome.
  • Specify the person’s authority explicitly—that is, which decisions they are authorized to make on their own.
  • Agree on reporting milestones at which interim results will be reviewed.

What is the opposite of micromanagement?

The opposite of micromanagement is controlled delegation, often referred to as empowerment or trust-based leadership. In this approach, the manager transfers responsibility for results to employees and no longer controls the process, but rather the agreed-upon output.

  • Clear agreement on objectives with measurable results
  • A defined scope of decision-making within which employees are allowed to act independently
  • Agreed reporting points instead of constant monitoring

This approach is an absolute must, especially in hybrid teams. When managing remotely, you must shift your focus from presence to results, because you no longer have the ability to visually monitor your team.

Moving Away from Micromanagement: What Should a Manager Do?

Overcoming micromanagement is a process that starts with the leader. If you decide to break this habit, these five steps will guide you toward lasting change:

  1. Conduct a self-assessment: Identify your personal triggers. Do you step in because you’re afraid of making mistakes, because you need to be in control, or because you don’t trust the team’s technical expertise?
  2. Categorize tasks: Sort by importance and urgency. Keep broad, strategic issues on your plate; assign all operational tasks clearly.
  3. Define expectations in writing: Describe the desired outcome, but not the path to get there. This will prevent your team from having to be corrected later on for deviating from the plan.
  4. Establish a reporting schedule: Agree on regular check-ins instead of ad hoc inquiries. Weekly or biweekly meetings replace the constant back-and-forth about status updates.
  5. Use tools to stay organized: Software that shows you at a glance who is working where, when office hours are scheduled, and when teams are meeting eliminates the need to constantly ask around.

How to Lead Your Hybrid Team with PULT Without Micromanaging

Micromanagement is a leadership style that comes at a high cost. It drives good employees to quit, undermines the quality of decision-making within the team, and creates legal risks related to organizational negligence and data protection.

The solution lies in controlled delegation. Clear goal agreements, defined decision-making authority, and agreed-upon reporting points replace constant micromanagement. In hybrid teams, the right tools help ensure that you maintain an overview without micromanagement. With PULT, you can keep track of everything without micromanagement:

  • Real-time overview without having to ask: With PULT Presence, you can see on a digital office map who is currently on-site and who is working remotely. Check-in happens automatically via the company Wi-Fi, so you don't have to ask anyone.
  • Weekly planning right in your calendar: Scheduled days in the office and working from home appear in Outlook and Google Calendar, so you don't have to track status emails. Team days can be scheduled fairly and proactively based on this information.
  • Answers at the touch of a button instead of endless back-and-forth: The AI assistant instantly answers questions like “Who’s in the office tomorrow?” via a simple chat interface. No group emails, no follow-ups, no micromanagement.

Automatic synchronization with your HR system: Vacation and absence data from Personio or HiBob is automatically imported into PULT. You can plan team events based on up-to-date information, rather than manually collecting availability data from team members.

{{onpage-cta}}