Establish a product owner / caretaker
Every solution needs a responsible person or role that collects requirements, clarifies priorities and coordinates further development.
Knowledge Base
Articles, materials and video links about core principles of digital transformation in schools will be added here later.
Start with why: clarify goals
Before technical implementation, it must be clear which problem is being solved and how value and impact will be recognized later.
Decisions before data before collection
Clarify iteratively: Which decisions need to be made? Which information is needed for them? Does that information already exist or must it be collected?
Apply the once-only principle consistently
Data should be collected only once where possible, embedded into the existing architecture and reused in suitable processes — with clean ID management where needed.
No automation without structured data
Automation only works reliably when data is collected in a structured way, is unambiguous, current and connected.
Create understanding of purpose and use
People need to understand why data, tests or workflows are used and what happens with the results.
Show, don’t tell: build prototypes
Ideas become understandable faster when they are visible as clickable or testable prototypes.
Provide guidance for broad use
Broad adoption needs clear instructions: preparation, execution and how to work with results.
Articles, materials and video links about core skills for digital transformation in schools will be added here later.
Report Scopes in Power Automate
Core skill for later articles, examples and video links.
Create Forms requests properly
Prepare and process requests from Excel in OneDrive or SharePoint.
Create Word templates
Fill Word documents from templates with Power Automate.
Approval workflows
Model approvals clearly in Power Automate.
Convert dates
Convert date values reliably in Power Automate.
SharePoint lists
Create lists, read from lists and write to lists.
Process JSON objects
Read, parse and reuse JSON from triggers, APIs or actions in a targeted way.
Write JSON objects
Build custom JSON structures for flows, APIs, Adaptive Cards and more complex data handoffs.
Create and use Solutions
Organize flows and components in Solutions.
Format dates
Format date values appropriately in Power Automate.
Send emails
Create and send emails from Power Automate.
Send Teams messages
Create and send Teams messages from Power Automate.
Send emails with options
Provide and evaluate choices via email.
Create Adaptive Cards
Prepare Adaptive Cards for Teams and Power Automate.
Short articles, examples and video links about Power Automate in school contexts will be added here later.
Always set Power Automate to English
Tip for development, troubleshooting, documentation and community research.
When to use Forms requests and when to use Power Apps?
Decision support for simple forms, structured input and app scenarios.
Excel is not a data source
Tip about when Excel is not robust enough and alternatives make sense.
Always work in Solutions
Tip for organizing flows, environments and components cleanly.
An introductory article with related video links about creating the first flow in Power Automate will be added here later.
Would you like to bring these principles into your staff, build competencies or develop your first flow at school? Get in touch with us.