Low-code tools are going mainstream
Purus suspendisse a ornare non erat pellentesque arcu mi arcu eget tortor eu praesent curabitur porttitor ultrices sit sit amet purus urna enim eget. Habitant massa lectus tristique dictum lacus in bibendum. Velit ut viverra feugiat dui eu nisl sit massa viverra sed vitae nec sed. Nunc ornare consequat massa sagittis pellentesque tincidunt vel lacus integer risu.
- Vitae et erat tincidunt sed orci eget egestas facilisis amet ornare
- Sollicitudin integer velit aliquet viverra urna orci semper velit dolor sit amet
- Vitae quis ut luctus lobortis urna adipiscing bibendum
- Vitae quis ut luctus lobortis urna adipiscing bibendum
Multilingual NLP will grow
Mauris posuere arcu lectus congue. Sed eget semper mollis felis ante. Congue risus vulputate nunc porttitor dignissim cursus viverra quis. Condimentum nisl ut sed diam lacus sed. Cursus hac massa amet cursus diam. Consequat sodales non nulla ac id bibendum eu justo condimentum. Arcu elementum non suscipit amet vitae. Consectetur penatibus diam enim eget arcu et ut a congue arcu.
Combining supervised and unsupervised machine learning methods
Vitae vitae sollicitudin diam sed. Aliquam tellus libero a velit quam ut suscipit. Vitae adipiscing amet faucibus nec in ut. Tortor nulla aliquam commodo sit ultricies a nunc ultrices consectetur. Nibh magna arcu blandit quisque. In lorem sit turpis interdum facilisi.
- Dolor duis lorem enim eu turpis potenti nulla laoreet volutpat semper sed.
- Lorem a eget blandit ac neque amet amet non dapibus pulvinar.
- Pellentesque non integer ac id imperdiet blandit sit bibendum.
- Sit leo lorem elementum vitae faucibus quam feugiat hendrerit lectus.
Automating customer service: Tagging tickets and new era of chatbots
Vitae vitae sollicitudin diam sed. Aliquam tellus libero a velit quam ut suscipit. Vitae adipiscing amet faucibus nec in ut. Tortor nulla aliquam commodo sit ultricies a nunc ultrices consectetur. Nibh magna arcu blandit quisque. In lorem sit turpis interdum facilisi.
“Nisi consectetur velit bibendum a convallis arcu morbi lectus aecenas ultrices massa vel ut ultricies lectus elit arcu non id mattis libero amet mattis congue ipsum nibh odio in lacinia non”
Detecting fake news and cyber-bullying
Nunc ut facilisi volutpat neque est diam id sem erat aliquam elementum dolor tortor commodo et massa dictumst egestas tempor duis eget odio eu egestas nec amet suscipit posuere fames ded tortor ac ut fermentum odio ut amet urna posuere ligula volutpat cursus enim libero libero pretium faucibus nunc arcu mauris sed scelerisque cursus felis arcu sed aenean pharetra vitae suspendisse ac.
"Remote work is bad for productivity". I've heard this a lot from office work advocates. But is this true? And how do we know? Let's unpack this a bit.
To look at this objectively, we need numbers.
As long as you track the proper inputs & outputs, productivity can be measured.
But what numbers? Well. Here are some metrics you can use.
1. % of goals & KPIs hit each month/quarter/year
2. Revenue per employee-hour
3. Revenue per payroll-dollar
4. Individual accountability metrics
1. % Of Goals & KPIs Hit Each Month/Quarter/Year.
I like this metric. At my last biz, we mainly operated off of the principle of "work however works for you, as long as the work gets done". Measured by KPIs & project completion. This is great in terms of progress towards stated goals which, if forecasted correctly, should directly translate into growth/revenue/cash flow. In a remote environment, it's freeing for the whole team to not have to care about clocking in & out or tracking time. Nice culture boost. But it does come with the trade-off of more granular productivity data.
2. Revenue Per Employee-Hour.
Great for teams with hourly pay, part time employees, or lots of contractors. You'll notice this is contingent on knowing the hours your team works. This is important! If your company's productivity is predicated on delivery of hours, you need to measure and know everyone's hours. I've used Harvest to track this at different times and effectively you are directly linking your inputs (hours) to outputs (revenue). In other words, the man-hours needed to service your revenue. "Standard" 40-hr weeks = 2,000 hours per year for easy calculation on fixed salaries.
3. Revenue Per Payroll-Dollar.
Hour tracking is great for calculating efficiency on time but of course, some time is more expensive. Senior employees, specialized contractors, etc. etc. In this case you can look at dollar yield on payroll. This effectively averages your specialized & leveraged staff across the organization and shows you how productive your team is on a dollar basis.
4. Individual Accountability Metrics.
I believe that everyone on your team, bar none, should have accountability metrics of some sort. These metrics should be visible to the whole leadership team, easy to find and reference, and updated as close to real-time as possible. When you run operations in this way, the office is basically a non-issue. Productivity will be measured the same way regardless of where everyone is.
Let's be honest, if someone can work half as much and get paid the same, they're naturally going to gravitate to that equilibrium. So you need proper management systems, training, and cultural habits to ensure productivity stays high. Done right... and you have a productivity BOOST, not just remote, but in the office too.
