How John Finnerty builds practical technology systems
A method note on diagnosis, reversible changes, source-aware project notes, documentation, and handover for practical New Zealand technology work.
Technical articles
Practical articles for New Zealand SMEs, owned web projects, and people who need clear technology handover.
Latest articles
These resources are written from project and support work: website launches, email authentication, source archive, local visibility, fibre, VoIP, and SEO basics. Each article links back to the relevant project, profile, or service context so the notes can be checked against current project notes and owned profile pages rather than read as isolated advice.
A method note on diagnosis, reversible changes, source-aware project notes, documentation, and handover for practical New Zealand technology work.
A plain security workflow for a small team: name the risk, assign the owner, confirm recovery paths, and check the result.
A plain-language security checklist for small teams that need safer access, second factors, and backup recovery without overcomplicating the work.
A plain review-request workflow for remote teams and service businesses that want honest customer feedback without pressuring people.
A practical way for solo consultants and SMEs to make their Google-facing description clearer and easier to trust.
Simple guardrails for using ChatGPT with SME prompts, client data, and team review in mind.
Reusable prompt patterns for common admin work, with review, tone, and privacy kept in the loop.
Simple review-request and response habits that help an SME build trust without sounding pushy.
Keep phone, email, hours, and service area aligned so customers are not left guessing.
Why competitors show multiple results for local searches, and how to build a useful service + article cluster without duplicates.
A checklist to sanity-check canonicals, redirects, indexability, sitemaps, structured data, internal links, and measurement.
Tenant basics, identity and MFA redundancy, mailbox hygiene, SPF/DKIM/DMARC, device sign-in, and handover safety.
A calm first-day checklist: contain the mailbox, remove forwarding/rules, reset access, and prevent repeat incidents.
A troubleshooting checklist to separate Wi-Fi from fibre, capture timestamps, run comparable tests, and build an ISP escalation pack.
Router placement, mesh vs access points, roaming issues, and what to measure before buying new hardware.
Symptoms, backups, access details, safe-mode tests, hardware notes, and handover info that reduces time and risk.
Protect the data, isolate the layer that is failing, and decide repair vs replace without guessing.
Practical boundaries for SMEs: what not to paste, what to mask, and how to keep admin workflows safe.
A plain-English process overview to reduce admin panic: what to keep consistent, what to check weekly, and what to hand over.
A practical guide to domain ownership, DNS records, website routing, SPF, DKIM, DMARC, rollback planning, and safe handover.
What to check before an SME website goes live: canonical URLs, forms, redirects, analytics, backups, handover, and search basics.
A project-proof guide for keeping source archive pages, case studies, metadata, screenshots, safe downloads, and profile evidence aligned.
How owned pages, profiles, schema, local relevance, citations, and project evidence help a professional identity make sense online.
A field checklist for separating device, Wi-Fi, router, fibre, SIP, VoIP, provider, and escalation evidence issues.
A practical SEO guide for New Zealand small businesses covering service pages, local proof, technical basics, content, SEO services, and measurement.
Reading paths
The articles are grouped around common SME and project handover problems. Use these paths to move from a practical guide to the matching support page, project evidence, or professional profile.
Start with the DNS and email checklist, then use the routing support page when a domain, DNS record, redirect, provider handover, or escalation path needs to be untangled.
Use this path after mailbox compromise or account takeover. Start with containment and persistence checks, then move into recovery hygiene and deliverability basics.
Use the launch and SEO articles together when a site needs better metadata, canonical URLs, analytics, sitemap coverage, internal links, and a practical post-launch check.
Use this path when you are publishing a project site and want clean canonicals, useful structured data, and a backlink pattern that connects the live page to the maintained write-up.
Start here when the goal is a clean local footprint that matches reality: consistent entity details, owned profile pages, and service pages that do not read like city-name templates.
Use the troubleshooting article when the fault could sit between Wi-Fi, router, fibre, SIP, VoIP, devices, provider settings, or incomplete handover notes.
Use the Microsoft 365 checklist when the real problem is access and identity. Pair it with the computer-repair triage notes when the machine itself is part of the failure.
Use this path when a device problem is blocking work. Start with safe triage and data protection, then move to a repeatable workflow for isolating the failure and deciding repair versus replace.
Related evidence
The articles connect back to current project evidence, service pages, and profile pages rather than relying on broad claims. For project-specific evidence, start with the Projects hub; for current professional context, start with the About page or the New Zealand and Christchurch profile pages.