Protokollseite für den Jour fixe anlegen
Every Monday at 8:00 the workflow creates the minutes page for the team meeting with agenda, outcomes and tasks and tells the facilitator.
Flowplan Marketplace
Documents, databases, workflows, whiteboards and looks for Flowplan – shared by the community, reviewed before they go live. One click and they're in your own instance.
Every Monday at 8:00 the workflow creates the minutes page for the team meeting with agenda, outcomes and tasks and tells the facilitator.
When a record's status changes, the people responsible and whoever created the record get a notification with the new status.
Every morning at 8:00 the workflow finds all records past their due date that are not done yet and sends the list to one person.
Every new day in the journal automatically gets prompts for the morning and evening: gratitude, the most important thing today and what I learned.
After every form answer the sender gets a confirmation by e-mail and the team a notification in the app.
Rate eight areas of life from 1 to 10, see where things run smoothly and where not, and set a next step per area.
The week at a glance: seven day columns, the three priorities, habits to tick off and room for notes.
Place stakeholders by influence and interest to decide whom to manage closely, keep satisfied, keep informed or monitor.
Before starting, imagine the project has failed: collect the reasons, pick the most likely ones, agree on countermeasures.
A retrospective about feelings: what made us mad, sad or glad – and which actions follow.
Cause-and-effect diagram: a problem at the head, possible causes along six categories – people, method, machine, material, measurement, environment.
“Ticket #12345” becomes a link to the ticket in the help desk – preset for Zendesk, for other systems just change the address.
Wiki notation: [[w:Begriff]] links the German Wikipedia article, [[en:Term]] the English one.
Short IDs of errors from monitoring like WEBAPP-3K become a link to the search in Sentry.
DOIs, arXiv papers, internet standards (RFC 9110) and vulnerabilities (CVE-2024-1234) become links to their official pages.
Issue keys like ABC-123 become a link to the issue in Jira as you type – for one or two project keys.
group/project!42 becomes a link to the merge request, group/project#7 to the issue – on gitlab.com or your own instance.
owner/repo#123 and #123 become links to issues and pull requests, abc1234 to the commit – just like on GitHub itself.
Sections of German codes (BGB, HGB, StGB, ZPO, AO, SGB V) and articles of the Basic Law become links to gesetze-im-internet.de.
Reflect on the year and plan the next: highlights, areas of life, lessons, letting go, goals and one word for the new year.
A script for a workshop: goal, outcomes, schedule with methods and materials, roles, preparation and follow-up.
Close the week in 20 minutes: clear the inboxes, look back, lessons learned and the three most important things for next week.
A short status report with traffic lights for schedule, budget and scope, progress, next steps and decisions needed.
A recurring process described as the binding way to do it: purpose, scope, responsibilities, steps, checks and change history.
A proposal to discuss before building: problem, goals and non-goals, proposed design, alternatives, risks, rollout and open questions.
Release notes for users: highlights, new, improved, fixed, important notes and upgrade steps.
Notes on a book or article: the main message, key ideas, quotes, own thoughts and what I want to put into practice.
Agenda and outcomes of the first project meeting: goal, roles, ground rules, risks and the first steps.
Onboarding new team members: preparation, first day, first week, first month – with contacts and a feedback conversation.
A running document for the weekly team meeting: fixed items, a topic backlog, outcomes and open tasks.
A structured job interview: schedule, the same questions for everyone, scoring by criteria and a recommendation.
A blameless review of an incident: impact, timeline, causes, what went well and actions with owners.
Formal minutes for a board, association or committee: attendance, quorum, agenda, resolutions with voting results.
A technical decision in the proven ADR format: context, decision, options considered and consequences.
Vendors and service providers with service, contact, contract end, annual cost, rating and data processing agreement.
Running subscriptions and contracts with monthly and yearly costs, term, notice period and next cancellation date.
Project risks with likelihood, impact, a calculated risk score, mitigation, owner and status.
Favourite recipes with ingredients and method, course, diet, time and rating – as a gallery.
Your own job search as a pipeline: openings, stage, salary range, contact, next step and notes on every conversation.
Track income and expenses by category and month – with totals, a monthly chart and a view of fixed costs.
A team's terms and abbreviations with definition, area, synonyms and source – as a list and by area.
Bugs with severity, status, environment and owner – as a board, a table and with a form for reports.
All action items agreed in meetings in one place: who, what, by when, from which meeting – with a view of what is overdue.
Neutral surfaces, a petrol accent, Work Sans and Fira Code with ligatures – for development and engineering teams.
Warm sepia, a rust-brown accent and Literata for headings – pleasant for long texts, journals and notes.
Cool surfaces, a deep indigo and Lexend as the interface face – modern, clear and pleasant in dark mode as well.
Sepia, a deep forest green, Nunito Sans and Merriweather – friendly and natural, e.g. for associations and education.
A strong dark red, Inter for the interface and Source Serif 4 for headings – like a well-set magazine.
Cool surfaces, a clear blue and IBM Plex for text, headings and code – sober and good for teams and customer portals.
Neutral grey, a muted sage green and the highly legible Atkinson Hyperlegible Next – few distractions.
On Fridays at 15:00 the workflow finds the records completed this week, has the AI summarise them, creates a report page and posts it to the chat.
Another service – monitoring, a third-party form – calls the workflow's address; it becomes a record in a database.
When a new page is created directly below a page, the workflow appends a link with a one-sentence description to the overview – never twice.
An e-mail to the workflow's address becomes a record: the AI reads the title, description and urgency, the sender gets a confirmation.
The AI puts every form answer into a category; each category makes a person responsible and notifies them. When the AI is unsure, the team lead decides.
Two days before the due date at 9:00 the people responsible get a push notification – only if the record is not done yet.
Phases and milestones on a time axis.
Strengths, weaknesses, opportunities, threats.
Activities, steps and stories ordered by release.
Keep doing, more of, less of, stop doing, start doing.