Operating model

A concise model for moving a demo from idea to a maintainable public release.

Scope

  • Applies to all published demos and case pages on laplandailab.fi.
  • Does not cover customer-internal systems without a separate agreement.
  • Each demo has one primary use case and a clearly bounded dataset.

Process steps

  1. Scope: define objective, user, data boundaries, and success signal.
  2. Build: working core flow first, then copy and usability pass.
  3. Check: technical smoke + security and content checklist.
  4. Release: stable URL, short change log, and fallback link.

Release criteria

  • No blocking console errors on the core flow (desktop + mobile).
  • Navigation, language switching, and primary CTA links work.
  • Page content states boundaries clearly with no “coming soon” placeholders.
  • External links use target="_blank" and rel="noopener noreferrer".

Maintenance approach

  • Ship small changes in separate commits.
  • Update sitemap and links in the same change set.
  • Log deviations briefly in a case note or release note.
  • Fix critical issues first; polish content after stability.