MVP

[ramanshah]

As I decommission Facebook and begin to move forward with my marketing strategy, I'm getting to need this more acutely. Here's the user story/MVP statement:

• In-browser, I have a ranked list of the people in my power circles in a table.
• I can log an interaction within 5 seconds with its date and an optional description.
• If I'm overdue to talk to someone in my power circles, their row changes color until I get back into compliance.
• I can bring back the view after closing the browser or restarting the computer because its contents were persisted to disk.

Would be nice to have to obviate nitty-gritty database migration:

• The people are organized into a directed acyclic graph based on how I met them: either through an institution or through an introduction by another person. This will support future graph analytics. I'd have to organize the ETL to get the people into the database in a topologically sorted order.

Stretch goal:

• I can re-order the list by dragging rows around. This would support really cutting the first iteration of my power circles.

ETL/adding people could be janky command-line stuff or one-time tedium for now. The inner loop is being reminded on a week-to-week basis that I'm overdue to connect with one of my peeps. I need this!!

[ramanshah]

Would I be satisfied with something like Airtable with a template like this one? It wouldn't have the DAG stuff but I might be able to live without it if I can re-purpose the development time for something more novel. https://airtable.com/templates/marketing-and-sales/exp7KcHbb6laaJkjU/personal-crm

I'd want to ascertain the following:

• Can I compute "Overdue" by power circle rather than an omnibus 45 days?
• Can the size of the power circles be capped at Dunbar's number without excessive friction?
• Relatedly: when someone gets promoted, do the people below them get properly demoted (to lower power circles)?

[ramanshah]

As of today, I'm in production with an internal MVP in Excel. It's literally a normalized table (would export cleanly to CSV or an SQL table) persisting the last interaction only. Substititing "browser" with "Excel," it satisfies the first four points above.

Getting experience with it will help spec out an in-browser version.

One tech scraping regarding the "stretch goal" is this: https://autodesk.github.io/react-base-table/examples/draggable-rows

[ramanshah]

Releasing an Excel MVP today.