Hacker News new | ask | show | jobs
by telecuda 1256 days ago
This has been our approach as we scaled from customer one to acquisition by bigco a decade later, and I'd still point to it as being a key driver of our success:

- Set a monthly meeting with a co-worker from each functional area (e.g. finance, support, sales). The meeting should be run by whomever has the best horizontal view of needs across the business, along with whoever is running point on development to clarify things.

- Go around the room and ask the question, "What's one thing (report/tool/insight/data/etc) that would make your job easier?"

- Track those requests on a shared document or board, giving stakeholders an opportunity to reprioritize their list (should never be more than a "top 3") each meeting

- PUNCHLINE: Commit to addressing one item from each department's top 3 every quarter. We did this starting early with engineer #2, but if you can't devote a FTE, divide and conquer among your current team.

10+ years later we have dozens of internal tools that have automated so much of what I see bigco still addressing by throwing people at it. It's never too late to start and it's a great way to build a love affair between your non-technical departments and developers!

1 comments

This is such an awesome approach! Kudos for putting this into action at your org. So many orgs that i've worked for/with might have similar ideas (at least for a couple of the noted items), but almost never implement any such thing due to distractions with other aspects of running the business.
Thanks! If you're looking for an easy place to start, look to tabular reports.

Ask a stakeholder (e.g. contract renewals team) to create an ideal report with maybe 5 rows of sample data in Google Sheets / Excel. A good example may be a list of customers, when their next renewal date is, who their sales rep is, etc. Ask a developer to turn it into a real-time (or nightly updated) internal web page, then once again, each quarter see if it needs to be made better. Sure, Salesforce and the like should have a lot of this data, but odds are you need a hybrid of info that leverages your own DB (e.g. usage, # of users). If a new vanilla Salesforce report comes out of that monthly meeting instead, hey, still good stuff.

We call this team "Ops" for short and more formally the "SaaS Operations" team since they satisfy all the internal bits that get help us run an efficient SaaS business. For reference, while we have a small team, it's 20% of our headcount (and a great place for interns/co-ops). Happy staff with the right tools stick around longer, are better at serving customers, and have more free time to work on more important goals.

That's great; thanks again!