2 ms·
Hierarchy starts in Documents. $name is employer name - .{$name} - {$name} Administrative = my personal corporate footprint. W-2s, onboarding, perf review
by hotsauceror 8y ago
Hierarchy starts in Documents. $name is employer name
- .{$name}
- {$name} Administrative = my personal corporate footprint. W-2s, onboarding, perf reviews, etc
- {name} Projects
- PMO Projects
- Leadership Projects
- Team Projects = internal initiatives
- Administrative Projects = stuff like, we need to update our service catalog portfolio or create a new RACI
- Application Projects = stuff like, “migrate the Fruitbasket database’s nonclustered indexes and staging tables to new filegroups”. Small technical projects, surfaced by our team
- {$name} Troubleshooting
- YYYYMMDD-$app-problem-desc = all the documents and data for a specific issue. Log dumps, AARs, executive summaries
- {$name} Management
- Vendors
- Budgeting + Forecasting
- Expenses
- Technical Portfolio
- Team Members
- SLAs / OLAs
- Audits
- Onboarding
- {$name} Documentation
- {$name} Forms and Templates
- {$name} Meetings = all meeting agendas and write ups. Each is a txt file named as YYYYMMDD-stakeholder/app-topic. Can be a tossup whether a meeting write up goes here or in a project folder.
- {$name} Change Management = docs and data for each change I’m either submitting or implementing. Each sub folder named by the Servicenow ID and a description.
- {$name} Operations = heat maps, log dumps, baselines, WIP documentation. Much of this is getting moved to github.