Skip to content
View markheck-solutions's full-sized avatar
  • Tulsa, OK
  • 04:14 (UTC -05:00)

Highlights

  • Pro

Block or report markheck-solutions

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
markheck-solutions/README.md

Hi, I'm Mark

I work in telecom infrastructure service delivery. A lot of my day job is dealing with messy handoffs, vendor delays, field coordination, escalations, and operational gaps that delay delivery.

This profile is where I experiment with AI to turn those problems into tools, workflows, and standards that make service delivery easier to manage.

I am not a traditional software developer. I use AI to help with the technical build, while I focus on the operational problem, the workflow, and whether the result is something operations would actually use and IT could reasonably support.


What I Work On

  • Service delivery operations – infrastructure delivery, migration readiness, vendor coordination, field execution, and escalations
  • Workflow tools – tools that reduce status chasing, manual follow-up, and unclear ownership
  • AI-directed builds – using AI to help prototype, document, validate, and improve operational tools
  • Readiness and supportability – checks, standards, handoffs, and support evidence so the work can survive past the first version
  • Decision support – scorecards, readiness models, dashboards, and structured follow-up workflows

Portfolio Demos

  • Vendor escalation tracking – tracking vendor delays, ownership, aging, next steps, and escalation paths
  • Carrier performance scorecards – comparing carrier/vendor performance across delivery, reliability, escalation, and readiness signals
  • Migration cutover readiness – tracking dependencies, risks, readiness, and go/no-go decisions
  • Supportability checks – building rules and checks so AI-assisted work does not turn into unsupportable prototypes

Pinned Loading

  1. carrier-performance-scorecard carrier-performance-scorecard Public

    TypeScript

  2. governance governance Public

    Python

  3. migration-cutover-readiness migration-cutover-readiness Public

    TypeScript

  4. pto-readiness-planner pto-readiness-planner Public

    Team Coverage and PTO Readiness Planner

    TypeScript

  5. vendor-escalation-tracker vendor-escalation-tracker Public

    TypeScript