Project Sauf: Rethinking Jira for the Whole Org

Project Sauf is a work management platform for planning projects, tracking progress, and automating workflows, designed as a ground-up rethink of Jira for one organization. The org ran engineering, HR, marketing, and personal task tracking in separate tools, so work fragmented and every cross-team question became a meeting. It turned out as one platform for every team: five workspace roles, five project types, and fourteen platform areas, told on this page through abstract, operable models instead of screens.

The research behind Project Sauf is synthesis, not a study: years of our own lived pain running work through Jira-style tools. Five wounds became the design brief. Fragmentation across teams, role-blind dashboards that fit neither a platform admin nor a first-week contributor, external consultants bolted on through workarounds, automation running silently until a surprise bill or a late failure, and answering “who changed what, and when” as an archaeology project across admin screens.

The research was a team’s shared pain. The role model is the design I drove. Project Sauf defines five workspace roles: Super Admin, Global Admin, Project Admin, Developer, and External User, and I made the workspace recompose for each one. The call I care most about: External User is a first-class role, not a workaround, holding scoped access sized to exactly what was shared.

Software projects sit beside Business, HR & Accounts, Marketing, and Personal ones, each with its own key, lead, work-item counts, and active iterations. A sprint board and a hiring pipeline are, structurally, the same thing: work moving through states. Bringing non-engineering teams in meant retiring engineering dialect, so issues became work-items and Goal became a first-class work-item type, over the platform depth power users expect, fourteen areas of it.

Admin visibility is the other half: the audit log is audit-ready by design, every entry carrying its category, actor, timestamp, and captured IP, filterable and inspectable in place, with backup, cleanup, and export controls beside the stream.

Every rule is the same sentence: a trigger, a condition, an action. The hard call was to wrap governance around that sentence instead of letting the engine run free. Rules are scoped Global or per-project, start life as Drafts, and a monthly run-quota meter makes cost visible before it is a surprise. Failures do not vanish: when a rule misfires, it surfaces on the admin dashboard, where someone accountable is already looking.