Thanks to everyone who asked questions & sent PMs while I was away. I’m gonna work my way through each of those.
As to why it’s taken me three weeks to post again…
10 percent of the delay was me
fucking around; 90 percent was due to an unexpected short-term gig that’s winding down this week. It’s been a huge time sink, but also enlightening and directly relevant to this thread.
The backstory is that a few months ago, I met a guy who’s a principal at a prominent NYC digital agency that handles web design and coding. I told him about my little no-name shop, and it turned out I’d done a modest web design/development project with lots of similarities to a major engagement his agency was then beginning.
Fast forward to mid-November. We’d emailed a couple times since meeting. Nothing past that. Out of the blue he called and asked to get drinks ASAP.
We met that evening and he gets right down to brass tacks: the project he told me about is going splendidly, except that it’s massively off schedule. As in, his estimated launch date for the website was
eight months later than what the contract stipulated. Mind, this project had only been under way three months!
I had to laugh. That is a royal fuckup that could only stem from a mixture overconfidence and total negligence.
We talked about how this happened, and sure enough, his agency and the client agreed to a project schedule that “felt” right without sitting down to assess the deliverables and the time needed to complete each.
That’s problematic on a $5k project. This is (guesstimating) a $500k project. Shit was
going down. The client already hired people who won’t have anything to do when their contracts start, because the site won’t be ready. Board members were intervening, jobs were supposedly in jeopardy, and obviously all those involved were sweating bullets.
The night after we got drinks, I met with the client and some folks from the agency. They offered me a consulting contract to help get the project back on track.
Which was funny, because
everybody else in that room had years of experience in this industry that I don’t have.
So along with tending to my own projects, I spent the last few weeks helping them. Broadly speaking, the process was something like this:
A) Discovery meetings –The agency conducted a brief discovery phase that left major questions unanswered. Critical, complicated functionalities were never discussed.
You don’t necessarily have to explain to the client how you’re going to
code every functionality, but you always need to discuss the user experience for any non-trivial function. Those discussions should produce a flowchart showing all possible outcomes, or at least a step-by-step walkthrough of the main outcomes.
For instance, the site they’re building will have news and informational articles. Registered users can save favorite articles in their account dashboard. That
could work a number of ways:
Option One: User clicks “save” icon on an article. Page title & link are added to their account dashboard under a list called “Saved Articles.” End of process.
Option Two: User clicks “save” icon on an article. A pop-up prompts the user to give the saved page a custom title. The custom title and link are added to their account dashboard under a list called “Saved Articles.” End of process.
Option Three: User clicks “save” icon on an article. They are redirected to their account dashboard, which includes a list called “Saved Articles.” Within “Saved Articles,” the user has created multiple subfolders. The user picks a subfolder for this latest article and confirms the save. End of process.
…and so on, through 500 possible permutations. A key goal of discovery is to decide which process is right for the site and commit it to paper. Then you design according to the written specifications.
Well, that didn’t happen in this case. Instead, they were figuring out these processes as they designed the site’s many, many templates. Each time the client or agency changed their mind about a process, it required the agency alter the designs of multiple page templates.
That’s a hugely time consuming process. It adds extra revisions to the design process and distracts the client from what they should be focused on—whether they’re happy with the look & feel of the designs.
Unsurprisingly, their design phase was proceeding at a glacial pace.
To rectify this, we (me & the agency’s guys) held dozens of additional discovery meetings with individual stakeholders and created detailed spec documents describing every template, feature, and function.
Then we turned those documents into directions for the agency’s designers. That will streamline their design work and make it much easier for them to satisfy the client’s expectations in only a few rounds of revisions.
This could easily have been done in the beginning of the project. That it wasn’t had already wasted a month, easy.
B) Responsive tech review – The site will be responsive with three breakpoints. That is, it will have versions tailored to desktop, tablet, and phone. Try resizing the your browser window on
this page to see what this means.
The hardest possible way to create a responsive site is to make separate wireframes and designs for each breakpoint.
The easier way is to use a responsive theme or framework. In simple terms, this method uses ready-made code to automatically rearrange & resize your desktop design so it looks good on tablets and phones, too.
Astoundingly, the agency had planned to do it the hard way. That was unnecessary for at least 75% of the site’s templates. My lead developer helped them create a responsive plan that drastically reduced the design & dev work for mobile platforms.
C) Rewriting the project schedule – With mobile design & dev simplified and many of site’s details clarified, we wrote a new project schedule.
Because the design phase will no longer be so “exploratory,” we were able to cut 1-2 rounds of revisions from nearly all templates. Using a responsive framework will save weeks if not months on coding.
The original target launch date was hopelessly optimistic, so the site will still go live months later than hoped. But not eight months—more like four or five.
Moral of the story...
My point here is twofold:
1) Project management doesn’t require expertise in any particular discipline. What it requires is that you be meticulous and think critically about the work your team does.
I’m no expert on responsive development or user-experience design. Far from it.
But I hire people who are, and I know how to ask them questions to make sure they leave no stone unturned in their thinking. Between my attention to detail and their expertise, we create good project plans, good concepts, and ultimately good websites.
Quote:Valhalla Wrote:
Am I the only one here who's read this and still confused on how to start?
I have no experience with wordpress or making websites.
2) If you don’t know shit about making websites, don’t worry. You won’t be alone in that regard.
The most interesting part of these past few weeks was talking with highly-regarded web dev professionals about all the ways they fucked up on this project. And I can’t help but think I would’ve done better, even though some of their past work makes my best work to-date look like fucking Geocities sites.
The agency’s lead guy on this job is a veteran creative director with major programming bona fides. On paper, you couldn’t be more qualified to run a project like this one. In fact, he still was in completely over his head.
But, props to him—whatever his faults, they didn’t prevent him from landing this half-million dollar deal. He took the job and when he found a snag he couldn’t handle, he hired someone (
![[Image: icon_biggrin.gif]](https://rooshvforum.network/images/smilies/new/icon_biggrin.gif)
) to handle it for him. And although he paid me well, my cut was a pittance compared to what he and his agency will walk away with.
That’s what I’m advocating here. It’s not programming or design or any specialized skill set—it’s plain old arbitrage. Sell a client on a website, build as much as you can, hire people to do the rest, pocket the balance, and repeat.
After the last couple weeks, I’m more convinced than ever that if you understand that process, you already know more than enough to begin.
——
That said, I’m working on a post outlining a simple project lifecycle, and then one explaining how you find and hire programmers (or other experts). Those and PM responses are coming this weekend, honest injun.
——
P.S. I appreciate all the encouragement w/r/t to selling this info somehow. To tip my hand, I do plan on monetizing it eventually, tho I’m undecided on whether a paid info product or content marketing material for my business is the route I wanna try first.
In either case, this forum gives me a perfect venue to put down my thoughts in rough draft form and get feedback on what’s most useful and what’s missing.
P.P.S. If the spirit is moving you to give
anyway, I suggest kicking me a few mBTC:
1149SF33LE4pGfE2FdPoWGZr842EL2h25H. Might make me a rich man someday.