Hello, fellow hackers!
I'm a long time reader and follow this community almost from the very beginning.
After reading a lot here and there, I got the idea that the best way to start a company is to ask questions first, before building anything.
So I'm asking you to validate this idea that I describe below in a set of questions:
Why people have to compete with each other on freelance boards? Why can’t we share the workload per project amongst individual contributors, as we do in our offices? Why people have to resolve to sub-hiring other freelancers and split big projects into chunks, acting a sort of project manager on behalf of a client (often w/o client knowing about such practice)? Why we have this invisible hierarchy of freelancers that includes experienced freelancers w/ high-starred profiles and an ocean of low-level first-time individuals, who have to take the smallest pieces of bigger projects w/o getting credit for it from the original client?
These are the sort of problems that remain largely unsolved on many freelance boards but have a robust and working solution in our traditional organizations.
Could we apply the sort of workload management we do at a web-agency to a group of strangers on the freelance board? Can we assemble a team of professional contractors just for a single project? Would they work together? Do we need to facilitate this process? How do we introduce a role of a team leader in such a structure? Would clients prefer to have their project picked up by a team of developers instead of choosing one sole contributor? Would it make sense for the client to pick what roles she needs for the project? Would we gain a more productive output from such entity than from a sole contributor?
What about time spent on the project? Would it be shorter due to the parallel work of multiple people or we’d waste more time in collaboration and communication issues? Who should be responsible if such a team does not deliver results on time, or at all? Would client have to pay partly for the work being done by some members, but not all of it? Would the unpaid members accuse their teammates of not setting them up for success? How should we rotate the team members that do not deliver their part of the job and when is the right time for it? Should the client worry about such rotations cause it would extend the project deadline?
What if some team member picks up the part that’s being neglected by others, should she get their cut of the pay? What about if different freelancers charge different amount of money per hour for their services? How would this affect the project budget? What about different personality types? Should we measure each team member’s performance based on 360 peer review results? Who would conduct and make decisions on such reviews? Should we build a graph of who likes whom and suggest project members based on personal preferences? Should we have a separate Project Manager freelancer position? How we’d identify leaders in each project and promote people to such a position? Would this person also contribute as a sole contributor? How do we define a measure of success for this manager role?
Thanks for reading!
What do you think? Do you share the same pain? Would something like this be useful to you? Would you pay for it? If so, how much?
Please let me know in the comments what you think about this idea!
I had a similar idea a while ago. I noticed that sites like 99design didn't really encourage people to follow a design proccess. just read the brief and show the finished thing. And considering the level they're at that doesn't help them much.
This is good for poeple to maybe win $100 every now and again. But as they are all junior designers or, more often, students who want to imporve. There isn't much scope for them to acutally learn to collaborate and follow a proccess better. and of coruse as a buyer there isn't much chance of getting anything half decent for your money.
How I thought about it would be that at the end of each stage people (not just the financer) could vote on who they think contributed the most and the money could be split. so for example on a logo project you might have a stage for selecting fonts, selecting colours and rough sketching ideas before the final stage of drawing the thing in illustrator. with discussion threads for each stage.
The advantages of this are that if you're a buyer you can be involved in the design proccess. if you're a designer you're actually learning about working with people, following a proccess and justifying your design decisions. This also means you have something worth sharing in your portfolio. Junior designers tend to show pretty pictures in thier portfolio which isn't much use without seeing the proccess they followed to get there. It also means there is less commitment to helpout if you're super busy and still maybe win a little money.
Of course this doesn't answer your question because I have no idea if this is a good idea either. just something I thought about once and suggested to another dev friend who said it sounded like chaos.
I am currious if you wanna chat about it and bounce ideas of someone tho.
Hey, Rob!
Thanks for your reply and ideas sharing!
I think your idea of having stages in the process of developing a final product is essentially splitting the big project into a bunch of small deliverable chunks. Which is fine, when there's a clear understanding of the final outcome of the project and the exact path to get there. But that (almost) never happens in reality according to my experience, unfortunately. Which is also perfectly fine if you follow the iterative approach to development and manage client expectations accordingly. And that is a skill that is largely missing currently on freelance boards, especially with junior level contributors. So, I agree there must be a solution to this problem...