Recently I was having a discussion with a team on a document they produced. Before I launched into my feedback, I wanted to make sure I understood what the goals and purpose of the document were. “What do you mean our goals?” What do you want to achieve with this document? After a bit of back and forth we got to what the purpose and goal of the document was and that helped me understand…
Home, the office, the coffee shop. You’re surrounded by noise. I bought a decent pair of noise-canceling headphones over the summer (mainly because I was FINALLY tired of having wired headphones and decided to go wireless). I love the moment when I put them on and it cancels out all ambient noise. Sometimes I don’t even play music, I just work in a bubble. It’s tricky at first because you’re constantly checking your phone to…
I’ve always thought the best way to test out an idea, to start a product, is to extend someone else’s platform. Build a component on what they have, test it out, see how it works, and take it from there. It’s a minimal investment, it’s less risk, it requires very little investment (your time). It might not be your final destination, but it’s the best way to see if there is a market there for…
The reviewer’s responsibility is to read what is put in front of them, acknowledge the content, and provide feedback where appropriate. If they don’t read it, they aren’t reviewing it, if they aren’t reviewing it they are not a reviewer. Finding reviewers is not easy – the good ones provide know the reason they are reviewing, they don’t rush it, they look at multiple points of view and provide feedback because that’s what is asked…
Don’t leave a meeting not sure what you are supposed to do next. Don’t leave a meeting knowing people who attended are not sure what to do next. Don’t attend a meeting if you’re not sure what it’s about or whether you need to be there. None of this is being rude (unless you’re being rude), it’s about holding yourself, your teams, and your meetings to a higher standard.