EB1 / O1 evidence map
This page helps you link work → proof → impact
What to publish
- Original troubleshooting write-ups with clear root cause and fix
- Reusable templates: IQ/OQ checklists, network validation steps
- Technical diagrams you created: NAT tables, VLAN maps, identity flows
- Before/after: reduced downtime, improved compliance, faster changeovers
How to format proof
- Problem statement
- Constraints and risks
- Step-by-step investigation
- Root cause
- Fix and verification
- Evidence: screenshots, logs, timestamps, SOP references
- Impact: time saved, defects reduced, audit readiness improved
Next action
Publish 2 posts per week for 8 weeks. Keep them short. Link them from your resume and LinkedIn.