Gareth

UX/Product geek with a passion for a prettier web, golf, real ale and eats his vegetables - Co-Founder of Skybase & Blocky #husband #dad

[Gareth @_gaz]

"A small team of A+ players can run circles around a giant team of B and C players." - Steve Jobs

[Gareth @_gaz]

@smarquezcochesa @jsahani_ai If you're mapping sites for client work specifically, I built Blocky for this: sitemap plus page structure plus the copy, with client sign-off built in. Whimsical is lovely but you end up rebuilding everything once content arrives.

[Gareth @_gaz]

@QoreebA Approving copy at the wireframe stage is the cheapest correction point in the whole project. The hard bit is your last line: clients react to grey boxes as if they're the design, so "this isn't the final design" needs saying about five times more than feels reasonable.

[Gareth @_gaz]

@jsahani_ai Real-time sitemap on the call is a strong move. It turns a vague brief into something the client can point at and correct while you're both still in the room, which is where scope arguments are cheapest to settle.

[Gareth @_gaz]

@PlantedSky Content collection is the quiet killer on web projects, and it's rarely that clients can't write. It's that a blank brief gives them nothing to react to. I built Blocky partly for this: draft the page in structure first, let them edit in context.

[Gareth @_gaz]

@socoloffalex The split that helps: structure and scope get signed off in writing early, taste stays yours. Once a client has agreed what each page has to do, most "make it bigger" notes get answered by the brief rather than by you defending your judgement.

[Gareth @_gaz]

@infomiho Works with humans too. Agreeing structure before anything gets styled or coded is the cheapest correction point in the whole process, whether the builder is an agent or an agency.

[Gareth @_gaz]

@rishabhjoshii Losing 8 hours to this on day 0 is a bargain. Most people find out in week three of build. Personas, sitemap and wireframe first means the expensive tools only ever execute decisions you've already made. Good luck with day 1.

[Gareth @_gaz]

@desgnwitkinsley The screen-by-screen breakdown with copy and states is the underrated bit. That output is basically a text wireframe, and it's the thing worth putting in front of a client for sign-off before Figma opens. Kills most late-stage rework.

[Gareth @_gaz]

@preciousmadeit_ The wireframe stage is where the real product decisions happen, so finishing it before opening the design tool is a habit that compounds. Most people skip straight to pixels and pay for it later. Nice work.

[Gareth @_gaz]

@shiyam_kashfiq Depth for anything expensive to unwind once build starts: structure, page purpose, what each section has to say. Speed for anything reversible later. Most projects get this backwards and spend the deep thinking on colours.

[Gareth @_gaz]

@remotesquadph Brutal. Staged sign-off is the only defence I've found: written approval per page as it's delivered, and final files held back until the last invoice clears. It won't stop bad actors, but it gives your contract a paper trail with teeth.

[Gareth @_gaz]

@iametod "The layout stayed almost identical from wireframe to launch" is the tell that the process worked — all the hard thinking happened before styling started. Design as refinement rather than rescue.

[Gareth @_gaz]

@webjuice_ie Exactly — AI compresses the drafting, but the checking and the sign-off stay human. That's the step clients actually pay for.

[Gareth @_gaz]

@TkYekinni Same at the page level — a rough wireframe forces you to decide what each section actually needs to say before fonts and colours eat the week. Structure first is a thinking tool, not a deliverable.

[Gareth @_gaz]

We got tired of chasing website copy through nine Google Docs, so we built ourselves a tool inside the agency. Sitemap, wireframe content and client sign-off in one place — approved section by section. It's free to try: https://t.co/UJf6VWpPv3

[Gareth @_gaz]

@NathanGeckler Amazing to see some of the hate a post like this gets. The guy is starting out in the industry and is making "something". He'll no doubt make mistakes and learn from them. Let's support young developers no matter where they are on their journey!

[Gareth @_gaz]

@josh_uglyasf @Pavegen 👍

[Gareth @_gaz]

@BradleyPhilpot @hampton_chris

[Gareth @_gaz]

@levelsio @MGMonge