Technically two people are a team, right? :P If it was only me I would use Org Mode, but that's not the case. Our projects are all artistic in nature, mostly screenplay collaborations, film...
Technically two people are a team, right? :P
If it was only me I would use Org Mode, but that's not the case.
Our projects are all artistic in nature, mostly screenplay collaborations, film criticism, YouTube, podcasts, etc . It's easy to get overly excited about this kind of stuff, but we need to follow up too. And we don't have an external demand that would incentivize us to put in the effort.
Even though we're only two people, we both have trouble sustaining long term goals, organizing schedules and information. My partner is a brilliant writer, but for him concentrating is even more of an issue than it is for me. He needs something visual. This tool must also work very well on mobile since he currently does not own a computer. It also must be graphical and easy to learn for someone that only knows Windows and MacOS.
To be more specific, I'm looking for something that allows me to track what we have done, what we're doing now and what we're going to do next. A calendar and some kind of notification system would be nice, but, as I say in the title, it must be free (I'm Brazil and our currency is worth nothing, so even the cheap is expensive for us...).
Google gives me dozens of results, reviews, etc, but it's hard to assess how good each tool is without experimenting it. And I would like to avoid learning an entire platform just to conclude it is subpar (I know this is largely unavoidable, but we can do better with a little help from our friends!).
Any suggestions? :D
 Even though our projects are artistic, their execution involves many things that are not artistic at all, such as understanding, budgets, legislation, registering our works with the copywriting authority, participating in public contests, networking, etc. There are lots of menial tasks that are easy to forget.15 votes
I'd like your input for an article I'm writing. Let’s say you’re starting a new IT project. It could be custom software; perhaps it’s a migration to cloud services; maybe it’s a shiny new IoT...
I'd like your input for an article I'm writing.
Let’s say you’re starting a new IT project. It could be custom software; perhaps it’s a migration to cloud services; maybe it’s a shiny new IoT project.
The point is that you're here to build something great. You’re in charge of the design (or an important part of it), and making sure that the resulting system makes everybody happy.
How do you make sure that you are interviewing the right people to find out what “make them happy” looks like? What do you do to get input from the people who matter for the project’s success… without inviting so many suggestions that it’s impossible to deliver everything?
Case in point: Ten years ago I was in charge of an online tech community. The company I worked for hired custom developers to build the software platform, but the developers never talked to me. They interviewed the boss, two levels above me (who just so happened to be the person who signed the checks) even though she had never used this online community or any other. Needless to say, the community software they delivered was horrible, missing basic-to-me features.
Formally this process would be called “identifying the project stakeholders” or “master the requirements-gathering process” but that seems too corporate-speak. I’m looking for real-world examples of what works and what doesn’t, so I can write a genuinely useful article with practical guidelines.
Note that this is NOT about the questions to ask those stakeholders; that’s another discussion. Here I am writing merely (merely!) about making sure you are speaking to the people whose input you need.
• How do you decide which people to ask for input? In what way do you find those people? How do you know when you have everyone you should?
• How do you decide whom NOT to invite? Where do you draw the line?
• Tell me about the manner in which you learned that lesson. (The hard way. Anecdotes are good.)
• If you want to be quoted (it's good for business!) tell me (via PM) how to refer to you in the article: Name, title, company name, short company description, URL.7 votes