Hi, So first I would have a direct conversation about hours per week he is willing and able to spend on the project. If that number is "2", then you're probabl

Hi, So first I would have a direct conversation about hours per week he is willing and able to spend on the project. If that number is "2", then you're probably going to need to replace him, and maybe try to get some shares back (or get him to give some shares to his replacement). If he's willing to give some real hours, look at how you're tracking his work & efforts. Do you have a trello board (or any easy alternative) for tracking what needs to get done? Ensure that it's trivial to discover what the highest impact piece of work is. How does he work, does he need a better development/testing environment to try out new things? Is he wasting time when he gets started because he needs to recreate his environment on AWS every time as it's destroyed to save money? Look for ways to reduce the friction in getting started, so 30 minutes waiting for food to arrive can be used productively, not just "getting started"