TODO and Notes
Todo
- Authenticating Clickup + Hubstaff
- How to set up your work schedule in Google Calendar
- Process for performance reviews
- Canadian Staff Payroll & tax info
- Project Management Team
- New project
- New task
- Pre-appointment process for strategy calls
- Post-appointment process for strategy calls
- Discussing technically-complex topics with clients
- Content standards for communication with clients
- Time-to-respond and time-to-clear standards for communication with clients
- Project delivery standards (tie it in a bow)
- Managing bugfix and troubleshooting tasks
- Becoming a dev-whisperer
External documentation resources
External documentation resources to consider folding into docs.teamtangible.com
Notes by Role
Project Management
Pre and post strategist call tasks and processes
Strategists should just be able to get on client-booked calls that show up on our calendar and never have to hunt information and people down before or after. Whatever we say on calls should get manifested into being by the PM team.
Right now we often have to hunt down PMs to force them to watch calls and follow up about whatever we said, and even then they often miss stuff.
Client communication standards
Setting some standards / expectations around responses would be good too
Things sit for scary amounts of time, or responses get copy-pasted clumsily from devs or strategists without being translated into stuff that is safe for a client.
Sometimes I see people giving really non-technical answers about issues, like "it's fixed!" and other times giving way too many details. The problem with both is that in the absence of detail, the client's brain will fill in the gaps with their anxiety, and with details that they can't understand, the same happens.
We have to provide technical detail, but in a way that is there not really to explain the technical details, but to re-assure them.
PMs have lately been too fast to "blame" hosting, or not correct impressions that an issue is hosting-related.
We need to provide a re-assuring level of detail, like if we're hunting down a long term bug that we have not been able to resolve yet, we need to do more than say "we're working on it" and need to explain what we've been trying at a high level, and why it's hard to pin down, in language they can understand.
It's not so that they actually understand any of the tech stuff, but just to re-assure them we care and are taking it seriously.
Also need to set some standards / benchmarks around response times and hold people accountable for them
Backend Development
WordPress/Frontend Development
- Where to find licenses
- subpage with links to download (https://docs.google.com/spreadsheets/d/1Nzv-1onvV4o3XpztTFzVHVwX14iQJF0loNtpnRXuFGc/edit#gid=0)
- https://www.gplkit.com/
Hosting
- TXP
- Jelastic/mightybox
- Client hosting accounts
- https://docs.tangiblexp.com/
- Quick staging/dev site https://app.instawp.io/
Design
Tools:
- Figma
- Affinity
- Fontforge
- icomoon
Product Support
Hosting Support
Loops & Logic:
- tangibletalk.com
- https://play.tangible.one (broken rn)
- Report a bug: https://forms.clickup.com/2294055/f/26097-14571/69M3S1J6DT2016WFSA
Membersync
Report a bug: https://forms.clickup.com/2294055/f/26097-18011/GMV4883JFZ7L6KFB8V
Processes
Project and Time management
- Hubstaff
Billing
- Xero
- Betterproposals
- Hubstaff (time reports)
- Coda (estimate logging)