That said, I myself am trying for such an arrangement, that is, multiple remote (bullshit) jobs.
> Do you have clear milestones and performance metrics?
Milestones yes, performance metrics not so much. Main reason here is that we serve different clients and we extend their existing strategies/work flows. So some times it's hard to measure stuff. Nonetheless in the past we did not pass milestones on time and thus questions were raised (esp. from clients).
So I guess we should start to build up some metrics. Any suggestions?
> Think about what actual problem you have
Main argument is about trust. We want to have provide an open work culture, so that everyone can openly speak about anything. If there are troubles (e.g. with performance) we try to encourage everyone to speak openly about it and to find solutions.
Secondly some times people are not as responsive (in terms of communication) as we initially agreed and usually re-negotiate every now and then.
And third: yes, there was decreased productity - and still is from time to time - so we openly try to find a solution with the affected people to increase it again. Unfortunately decreased productivity is not backed by a lot of data, but by day to day
So I'd guess confirmation bias is also some factor for the company.
> Do you pay your developers well enough [...]
I'm not in the position to know exact numbers, but what I've heard so far is that they are compensated well. Nonetheless I don't know exact details. But I know that they don't get a compensation like people in Europe.
----
Yes, one could boil this down to control (as mentioned in another comment), but I don't think it's that easy. If we agree on a contract, then I (personally) expect that each site of the contract is fullfilling their duties. And our contract clearly states that the company must be informed about side-projects and other work. There is no direct penalty if one works a second job, but there will be a huge trust issue.
With my customers I am continuously negotiating goals, milestones, expectations, costs, and risks. I want my customers to understand what they are paying for and what I am committing to. As much as possible I try to charge for deliverables rather than for my time, but sometimes customers prefer to pay by the hour, or on a retainer. However we work that out I try to always make sure my customer and I are clear about what they expect from me and how much time that will take and what it will cost. That comes down to communication, and generally we iterate on their goals.
Measuring productivity is a hard problem, and even harder for creative people who may have large variations in their own productivity over time, and aren’t directly comparable to other individuals. I would start with setting clear goals and measurable deliverables and then getting the employee to commit to those. That means breaking the work down into measurable pieces, which will happen one way or another, so it’s probably best to do that work up front so no one gets surprised.
Communication is something you can set clear expectations about. For example I commit to my customers that I will answer routine emails the same day, and urgent emails or phone calls immediately. I ask my customers to respect my time and if everything turns into an emergency with them we’ll have to talk about that.
You should have some idea of what fair pay or market rate looks like for the people you employ. Personally I don’t believe it’s fair to pay people less because of where they live — everyone should get paid according to the value they add, whether they live in London or Bangalore. If you don’t pay people enough they will take on other jobs, or look for a job elsewhere.
I would not sign a contract that obliged me to inform my employer or a customer about other work. Sometimes issues of competition and intellectual property come into play. If someone is inclined to act unethically or break the law a contract clause isn’t likely to stop them. If you ask employees to agree to inform you of outside work, what do you agree to in return? Do you inform your employees about all of your customers? How much the company gets paid by customers? Whether the founders have other business commitments?
Bottom line is you pay people for their work, period. You can’t expect loyalty or openness or trust, especially if it’s one-way in the company’s favor. People are loyal to employers who treat them well. They trust employers who trust them and treat them with respect. How open someone is with their employer is really up to them — they don’t owe that to their job.
That's what I'd like to see from everyone (generally spoken). Anyhow, thanks for your thoughts and sharing your experiences! There is a lot of value in it.
I guess communication is - as usual - a huge factor in all of this (from each party).
----
> For example I commit to my customers that I will answer routine emails the same day, and urgent emails or phone calls immediately.
That's very valuable and honest from you. But it's you who is doing that. Not everyone acts like that (from my experience). So how would one be able to create a proper adherence for such a commitment (that was agreed on while signing the contract)?
At all times the manager should know what people are working on, when to expect delivery, and know how to detect schedule/cost slips early on. The programmer(s) should know exactly what they are supposed to be doing, and what “done” looks like — what their deliverable is. What I actually see most of the time is vague requirements like “make an e-commerce site in six months” from management (or in my case, customers), and the programmers left on their own to figure that out. Then the team spends five months arguing about programming languages and tools and the “best” approach to edge cases while nothing gets delivered, and their manager is not paying attention. If the manager set the deliverables the team could work to deliver in a clear way. “Site structure with navigation but no content or functionality in two weeks,” for example. Give the team a few days to decide on language and tools and so on then move forward.
With short iterations it should be obvious fairly early if the tasks are too vague, or the estimates are way off, or if the team is not working on the agreed-to goals. When those problems become apparent the manager (or customer) and the programming team identify the cause and adjust so the next iteration (call it a sprint if you want, same thing) goes better. The team should be delivering all the time — manager should not allow 80% of the schedule to go by without seeing continuous progress. In my case I’m putting something in front of my customers every few days, and my deliverables are easy-to-measure things like (for example) import these CSV files into a Postgres cloud instance, or verify that the addresses users enter have valid ZIP codes. With a more experienced and “gelled” team you can make the deliverables a little broader.
I’m describing Agile development, but not the rituals and nonsense that have made the term almost meaningless. Iterative development with clear tasks and deliverables, and a feedback loop with the customer, right from the beginning.
As for communication, you can set those expectations and if the programmer is not talking to the team, or the manager, or customer, within the time limits you both agreed to, you have a performance issue to deal with. Poor communication sinks projects more often than not understanding binary trees. From my own customers the number one thing I hear is “The last developers stopped answering my emails and phone calls.” I make a point to always answer and keep my customers informed, which puts me in the top tier of freelancers even if I’m not the most technically awesome programmer.
you need to hit them with low salaries and high taxes, when they try for a better life quickly squash that crap with overly broad non-competes
welcome to Europe
how about paying employees adequately to a point where they don't have to work multiple full time jobs at a time, such an outlandish idea
If the employer sets clear performance expectations and has some way to measure performance, then employees either meet expectations or they don’t. If they don’t the employer can take remedial action, up to letting the employee go. It doesn’t really matter if the poor performance or low productivity was caused by another job or the employee playing video games or watching TV all day.
There’s some irony in the business the OP describes hires programmers out to multiple customers. That means the owners and managers of the company are working multiple jobs.
Interesting point. Didn't thought about that yet! I wouldn't say the situtations are exactly the same, but they share a lot of details.
nailed it :) its fine when we pocket the US cost / EU dev salary difference, but its not ok when you try to go solo and do the same
its not exactly breakthrough idea, don't get weird when someone else tries to have a go at it
We aren't talking about people holding mulitple low-paying jobs to make ends meet. It's mostly people in well payed positions taking advantage of being remote.
It's a tricky problem that I don't necessarily have an answer to. My point was that it's misleading to compare people who have to work multiple jobs to survive with people who are making hundreds of thousands at each job.
Example from https://news.ycombinator.com/item?id=29784608:
> As far as the money goes, my math goes like this:
> - 1 job: 250-300K cash, 250-300K equity (at the high end, higher if I moved to management)
> - 4 jobs: My current situation is 225K avg cash (including bonuses) per job, 100K avg equity per job
You can't look at this and say (like the GP comment did) "how about paying employees adequately".
It’s up to the employer to set clear performance expectations and measurements, then handle employees who don’t meet those expectations as a job performance problem. If the employer can’t do that basic management work, preferring to pry and control and intimidate their employees into submission, they deserve what they get.
I don’t understand the argument “They are already well-paid so they shouldn’t look to make more money.” Try that on the C-suite execs who sit on multiple corporate boards.
Yes, and that's the question that OP is asking - how do you set those expectations and measurements. It's a starting point for the whole conversation, not the end of it.
> I don’t understand the argument “They are already well-paid so they shouldn’t look to make more money.”
I've never made this argument or seen anyone else in the thread make this argument.
> First of all, I'd like to figure out how we can identify someone working more than we are aware of. Generally it would be fine for me (/us) what people do in their non-work time, but if it affects our work, then it's not acceptable. So how can we identify such a situation?
The question indicates the OP doesn’t have a way to measure performance, and instead focuses on identifying employees who might have other jobs.
> I've never made this argument or seen anyone else in the thread make this argument.
I must have misunderstood what you meant by this:
> We aren't talking about people holding mulitple low-paying jobs to make ends meet. It's mostly people in well payed positions taking advantage of being remote.
One could read “taking advantage of being remote” more than one way, but in the context I read it as people already paid well taking advantage of their employer.
While this statement is true, I'm nonetheless interested in a good ways to measure and agree on performance metrics. But please metrics that do not affect (especially the remote) in a negative way. Personally I'm not so much of a fan to put number of people's performances, especially in development, which makes it really hard some times.
If your performance metric comes down to “Employee has blocked out eight hours per day exclusively to me” then you’re a terrible manager and employer.
I would almost play along with bullshit check-in calls like you describe if I could call my manager and the company executives randomly to check if they’re actually working too, and not golfing or buying NFTs with my withheld taxes.
whether that takes eight hours or four, and whether it happens during normal business hours or at 3 am
So they could very well only work 2 hours and say that's all they can work and call it done, work 3 others jobs I could call my manager and the company executives randomly to check if they’re actually working too
I didn't say it was random callsEmployers can’t give employees “full freedom.” Nor can they prohibit the employee doing whatever they want on their own time. Forcing employees to commit to one job is just coercion unless there’s some clear business rationale behind it, not just control and an attitude that the employer owns the employee.
In that context you can take your math and divide by 10 to get the mainland EU average for software engineer salary (~40k). With up to 50% tax rate gives incentive to have multiple jobs if your diet consists more than of plain yogurt and bread.
Think about what actual problem you have if some of your remote developers have two jobs. Can you measure the costs or risks? Or do perceive it as a betrayal or lack of control?
Ed Zitron wrote “If someone gets their work done to a high quality and on time and also happens to be working another job, you do not actually have a problem, and if anything, you’re lucky to have them.”
https://ez.substack.com/p/the-two-jobby-problem