Skip to content

Revise corporate telos document for clarity and detail#17

Open
mtomas7 wants to merge 1 commit intodanielmiessler:mainfrom
mtomas7:main
Open

Revise corporate telos document for clarity and detail#17
mtomas7 wants to merge 1 commit intodanielmiessler:mainfrom
mtomas7:main

Conversation

@mtomas7
Copy link

@mtomas7 mtomas7 commented Feb 5, 2026

General Notes

  • My Goal was to extend the document structure, make it more granular, and use same structure for company and team(s).
  • I expanded Company's structure a bit, and moved all company items and Security team items under parent sections to have clear hierarchical structure.
  • It looks that in the original version Security Team part was generated twice with 2 somehow similar content - second run is under "Security Team Narrative". For example, "Security Team KPIs (How we measure the team)" is almost the same as "How We're Doing". I converged similar sections according to a structure that was introduced with the Company and also added some Team sections to the Company.
  • Added some explanations for the user, as this is a template to be adapted.

Thorough List of Changes

  • Document Purpose
    • Streaming updates (Activity) explanation was expanded into a separate paragraph.
    • Some other minor updates.
  • Company Goals renamed to Company Strategic Priorities & Goals under Company Strategy Stack
  • Added: Company Strategies (How we win)
  • Company KPIs renamed to Company KPIs (How we’ll measure progress)
  • Mirroring Security Team profile, added Company Risk Register (The things we're most worried about)
  • Added Company CURRENT STATE to record Company-level events that affect Security Team.
  • Used same structure for the Security Team
  • Moved duplicate sections from Security Team Narrative
    • Background > Security Team Overview
    • Current Risks > Security Team Strategy Stack: Security Team Risk Register
    • Security Team Strategies > Security Team Strategy Stack: Security Team Strategies
    • How We're Doing > Security Team Strategy Stack: Security Team KPIs
  • Moved Security Team Strategies > Security Team Strategy Stack: Security Team Strategies
  • Moved Team > Security Team Overview: Security Team Members
  • Renamed CURRENT STATE > Security Team CURRENT STATE
  • Moved Infrastructure Notes > Security Team Overview

Updated Document Structure

  • Document Purpose
  • Alma Security Strategic Performance & Quality Assessment (SPQA) Profile
    • Company Overview
      • Where Company Fits in the Bigger Context
    • Company Identity
      • Company History
      • Company Mission
      • Company Vision
      • Company Values
    • Company Strategy Stack
      • Company Strategic Priorities & Goals (What we want to achieve)
      • Company Strategies (How we win)
      • Company KPIs (How we’ll measure progress)
      • Company Risk Register (The things we're most worried about)
    • Company CURRENT STATE (KPIs, Metrics, Project Activity Updates, etc.)
  • Alma Security - Security Team Strategic Performance & Quality Assessment (SPQA) Profile
    • Security Team Overview
      • Security Team Members
      • Infrastructure Notes
    • Security Team Identity
      • Security Team Mission
    • Security Team Strategy Stack
      • Security Team Goals
      • Security Team Strategies (How to achieve the Goals)
      • Security Team KPIs (How we measure the team)
      • Security Team Risk Register (The things we're most worried about)
    • Security Team Projects
    • Security Team CURRENT STATE (KPIs, Metrics, Project Activity Updates, etc.)

## General Notes

- My Goal was to extend the document structure, make it more granular, and use same structure for company and team(s).
- I expanded Company's structure a bit, and moved all company items and Security team items under parent sections to have clear hierarchical structure.
- It looks that in the original version Security Team part was generated twice with 2 somehow similar content - second run is under "Security Team Narrative". For example, "Security Team KPIs (How we measure the team)" is almost the same as "How We're Doing". I converged similar sections according to a structure that was introduced with the Company and also added some Team sections to the Company.
- Added some explanations for the user, as this is a template to be adapted.

## Thorough List of Changes

- Document Purpose
	- Streaming updates (Activity) explanation was expanded into a separate paragraph.
	- Some other minor updates.
- Company Goals renamed to Company Strategic Priorities & Goals under Company Strategy Stack
- Added: Company Strategies (How we win)
- Company KPIs renamed to Company KPIs (How we’ll measure progress)
- Mirroring Security Team profile, added Company Risk Register (The things we're most worried about)
- Added Company CURRENT STATE to record Company-level events that affect Security Team.
- Used same structure for the Security Team
- Moved duplicate sections from Security Team Narrative
	- Background > Security Team Overview
	- Current Risks > Security Team Strategy Stack: Security Team Risk Register
	- Security Team Strategies > Security Team Strategy Stack: Security Team Strategies
	- How We're Doing > Security Team Strategy Stack: Security Team KPIs
- Moved Security Team Strategies > Security Team Strategy Stack: Security Team Strategies
- Moved Team > Security Team Overview: Security Team Members
- Renamed CURRENT STATE > Security Team CURRENT STATE
- Moved Infrastructure Notes > Security Team Overview

### Updated Document Structure

- Document Purpose
- Alma Security Strategic Performance & Quality Assessment (SPQA) Profile
	- Company Overview
		- Where Company Fits in the Bigger Context
	- Company Identity
		- Company History
		- Company Mission
		- Company Vision
		- Company Values
	- Company Strategy Stack
		- Company Strategic Priorities & Goals (What we want to achieve)
		- Company Strategies (How we win)
		- Company KPIs (How we’ll measure progress)
		- Company Risk Register (The things we're most worried about)
	- Company CURRENT STATE (KPIs, Metrics, Project Activity Updates, etc.)
- Alma Security - Security Team Strategic Performance & Quality Assessment (SPQA) Profile
	- Security Team Overview
		- Security Team Members
		- Infrastructure Notes
	- Security Team Identity
		- Security Team Mission
	- Security Team Strategy Stack
		- Security Team Goals
		- Security Team Strategies (How to achieve the Goals)
		- Security Team KPIs (How we measure the team)
		- Security Team Risk Register (The things we're most worried about)
	- Security Team Projects
	- Security Team CURRENT STATE (KPIs, Metrics, Project Activity Updates, etc.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant