Design artifacts
Five artifacts tracing the NimbusWiz design process from napkin sketch to screen-level wireframe.
Five artifacts tracing the NimbusWiz design process from napkin sketch to screen-level wireframe.
The navigation hierarchy, URL schema, and content organization behind this portfolio site.
How this portfolio is structured, labeled, and organized: and why.
what the combined journey maps reveal about the product design
Two users, one pipeline, three critical divergences: paired journey maps for a professional DevOps Engineer and a non-technical casual user.
NN/g-style journey map for a DevOps Engineer running a system through the NimbusWiz pipeline, with a modelled anxiety curve and design opportunities tagged by type.
Building an iterative content audit system in Notion using MCP: and what iterative auditing reveals that one-shot audits miss.
Three personas NimbusWiz is built for, presented as a comparative artifact: DevOps Engineer, System Administrator, and Technical Manager, plus the four tensions between them.
How I'd structure a documentation program: user segments, prioritization, instrumentation, and cadence.
Content types, controlled vocabulary, labeling conventions, and metadata model for this portfolio site.
NN/g-style journey map for a non-technical owner moving a vintage Nimbus2000 through the NimbusWiz pipeline, paired with Mark's journey for cross-comparison.