Public landing page for Marco Policani's Principal / Director-level portfolio, PMO, executive operations, AI-assisted workflow governance, decision support, and operating-model portfolio.
Live site target:
This site is the search-friendly front door for a portfolio that otherwise lives across GitHub repositories and GitHub Wiki pages. It is intentionally written to help recruiters and hiring leaders see the target lane first: Director or Principal roles in PMO, EPMO, PPMO, portfolio governance, program operations, executive operations, and Chief of Staff roles centered on cadence, portfolio visibility, and decision support.
The public positioning should make Marco discoverable for portfolio governance, PMO leadership, executive operating cadence, Principal portfolio management, Director PMO, AI-assisted workflow architecture, evidence-bound decision support, delivery readiness, value realization, and practical AI workflow governance without implying CEO, VP, GM, formal Chief of Staff, software engineering, ML/data-science, model ownership, product-owner, or production SaaS ownership.
- Lead with role fit and operating problems, not a flat repository list.
- Treat experience evidence as the primary support layer for public claims about scale, stakeholder altitude, and operating context.
- Keep the top-level website structure explicit:
portfolio.htmlfor Role Fit,operating-history.htmlfor Case Studies,artifacts.htmlfor How I Work,modules.htmlfor Workflow Systems,proof.htmlfor Evidence,resources.htmlfor Resources, and the home contact section for Contact. - Anchor the public headline on Principal / Director-level portfolio, PMO, and executive operations.
- Treat Chief of Staff as a target lane only when the role means executive cadence, cross-functional operating rhythm, portfolio visibility, and decision support.
- Keep PMO, portfolio, AI workflow governance, readiness, controls, and value modules framed as proof-of-concept workflow assets and public-safe examples. They support the portfolio but do not carry the executive credibility claim by themselves.
- Keep the career, job-search, and writing tools in a distinct Resources lane. They are community resources, not core executive-portfolio proof, even though they can still show broader workflow craft.
- Use SEO/search language in headings, metadata, and navigation, but keep product prose grounded and specific.
/is the simplified hiring-manager front door and evaluator path./portfolio.htmlis Role Fit: it explains role fit, executive operating problems, and the operating-history bridge./operating-history.htmlis Case Studies: it provides public-safe experience evidence and links specific experience claims to the portfolio routes or modules they support./artifacts.htmlis How I Work: public-safe routes from unclear signal to accountable review./modules.htmlis Workflow Systems: downloadable proof-of-concept modules grouped by operating lifecycle./proof.htmlis Evidence: proof taxonomy, public-safety boundaries, scope guardrails, and AI workflow governance boundaries./resources.htmlis Resources: career, job-search, and writing resources for the broader community; it is not part of the main executive proof path.
- GitHub profile: https://github.com/policani
- Portfolio index: https://github.com/policani
- Portfolio artifacts source pages: https://github.com/policani/Policani/tree/main/wiki
- Anonymized artifact source: https://github.com/policani/operating-patterns
The site uses public-safe, generalized language. Do not add employer names, client names, logos, screenshots, internal terminology, exact dates, financial figures, proprietary processes, or details that could identify a prior organization.
Site code, styles, and scripts are licensed under MIT. Written content and other non-code portfolio materials are licensed under CC BY 4.0 with attribution to Marco Policani. See LICENSE.md.