Archived. This work is kept for reference and is no longer maintained.

Tickly

Tickly was an employee IT lifecycle management project. It is archived: product work continues in TenCtrl, a Microsoft 365 support operations workstation.

Overview

Tickly is the software product line connected to ABD Labs: an employee IT lifecycle management platform intended to help organize identity, onboarding, change and offboarding workflows.

Problem

Employee lifecycle work often crosses HR, IT operations, identity, devices, access reviews and audit evidence. Tickly is being developed as a focused software project around that operational problem space.

Constraints

  • Do not claim production customers, certifications or live enterprise deployments that are not verified here.
  • Keep Tickly operationally independent from lab infrastructure.
  • Use future Microsoft lab data only as synthetic or read-only evidence after the lab is approved and built.
  • Present the project as in development until implemented capabilities are documented and verified.

Approach

Treat Tickly as a serious product and engineering project while keeping the public portfolio honest: describe the domain, status and intended lifecycle scope, then link future implementation evidence only when it exists.

Key decisions

Separate product work from lab infrastructure.

Tickly should be able to evolve as software without depending on a Windows lab runtime or exposing lab administration surfaces.

Alternatives considered

  • Use the lab as a required backend for the product.
  • Publish unverified product claims before case-study evidence exists.

Use ABD Labs as the evidence layer.

The portfolio can document architecture, implementation notes and future lab-backed testing without overstating production maturity.

Alternatives considered

  • Hide the project until everything is complete.
  • Market the product without technical evidence.

Result

Tickly gives ABD Labs a software-development track alongside infrastructure and automation work, while the portfolio keeps its public claims bounded by verified evidence.

Learnings

  • A credible product portfolio should distinguish product direction from completed production evidence.
  • Lifecycle management is strongest when software, identity operations and automation are documented together.
  • Lab integrations should be read-only or synthetic until the lab is stable.

Status

Tickly is archived. The support and lifecycle problem it explored continues in TenCtrl, which starts from everyday Microsoft 365 support work and verified evidence.

Evidence Boundary

This page documents Tickly as an archived software project. It does not claim production customers, certified compliance status, completed Microsoft tenant integrations or live enterprise deployments.

Future Tickly case studies can be added when there is verified implementation evidence, screenshots, code excerpts, architecture notes or lab-backed test data suitable for public release.

All projects